Re: [onap-discuss] Some thoughts about ONAP Microservice Architecture for Casablanca and beyond: Service Mesh, Centralized Authentication and unified API standards

[zhao.huabing]

Hi Parviz,


Is this scheduled for Monday? Sorry I missed it. Could we move it to the next 
call, is that this Friday?


Thanks,


Huabing







Original Mail



Sender: ParvizYegani 
To: zhaohuabing10201488;Christopher Donley(Chris) 

CC: onap-arch-tiger-t...@lists.onap.org 
onap-discuss@lists.onap.org 
Manoj K Nair 'Vul, 
Alex' 
Date: 2018/03/19 14:59
Subject: RE: Some thoughts about ONAP Microservice Architecture for Casablanca 
and beyond: Service Mesh, Centralized Authentication and unified API standards 




Hi Huabing,


 


Thanks for launching the discussions on ONAP Microservices architecture. Right 
timing! This is a very important topic that we need to consider for the ONAP 
target  architecture (R3+)!


 


I added the following item to the agenda for today’s tiger team call:


-  ONAP Microservices Architecture for Casablanca and beyond

Please share your slides prior to the call. I hope Manoj, Alex, Manish and 
other folks who have been quite active in driving this work in ONAP can join 
the call as well.


Thank you


Parviz


 


---


PARVIZ YEGANI, PhD 
Chief SDN/NFV Architect


CTO Office, Cloud Network Solutions


 


FutureWei Technologies, Inc.


2330 Central Express Way


Santa Clara, CA 95050, USA


Phone: +1 (408) 330-4668


Mobile : +1 (408) 759-1973


parviz.yeg...@huawei.com 


 


 


 


From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn] 
 Sent: Wednesday, March 14, 2018 4:01 AM
 To: Parviz Yegani ; Christopher Donley (Chris) 

 Cc: onap-arch-tiger-t...@lists.onap.org; onap-discuss@lists.onap.org
 Subject: Some thoughts about ONAP Microservice Architecture for Casablanca and 
beyond: Service Mesh, Centralized Authentication and unified API standards 


 

Hi all,

I'd like to share some of my thoughts about ONAP Microservice Architecture for 
Casablanca and beyond

 

1. Service Mesh

Service Mesh is the next generation of Microservice approach, which can bring 
lots of benefits to ONAP and its users at both the development and operation 
sides. Such as 


· the separation of business logic and Microservice 
infrastructure(communication, security, metrics etc)


· allowing free choice of development tech stack


· flexible route rules to enable traffic steering and canary release


· monitoring and tracing visibility


· fault injection for resiliency testing, etc

We should take service mesh into consideration. There are multiple choices on 
the table right now, given its tight relationship with kubernetes which is used 
for ONAP deployment, I suggest we give Istio a shot in Casablanca. MSB project 
is investigating  the possibility of integration of Istio and ONAP right now. 

 

2. Centralized Authentication

ONAP is a huge system consisting of many services. Currently, different 
services such as AAI, SDC, Policy etc. have their own authentication process, 
which makes ONAP difficult to use and adds burden to the individual project to 
enforce the cross-project  authentication logic. We need to consider 
implementing some kind of centralized authentication, which means user login 
once and can access all the services. We also need to consider how to secure 
the access of 3-party systems by using API token or OAuth.

 

3. Unified API standard

Most of the projects produce RESTFul APIs for consuming, but in a 
none-consistent way. we need to define some unified standards/best practices on 
the REST API definition across the ONAP projects such as versioning, url, error 
code.  There is a draft in the  wiki page: 
https://wiki.onap.org/display/DW/RESTful+API+Design+Specification

BR,

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

Re: [onap-discuss] Some thoughts about ONAP Microservice Architecture for Casablanca and beyond: Service Mesh, Centralized Authentication and unified API standards

[zhao.huabing]

Sure, I'll send out the slides later today before our call.











Original Mail



Sender: ParvizYegani 
To: zhaohuabing10201488;Christopher Donley(Chris) 

CC: onap-arch-tiger-t...@lists.onap.org 
onap-discuss@lists.onap.org 
Manoj K Nair 'Vul, 
Alex' 
Date: 2018/03/19 14:59
Subject: RE: Some thoughts about ONAP Microservice Architecture for Casablanca 
and beyond: Service Mesh, Centralized Authentication and unified API standards 




Hi Huabing,


 


Thanks for launching the discussions on ONAP Microservices architecture. Right 
timing! This is a very important topic that we need to consider for the ONAP 
target  architecture (R3+)!


 


I added the following item to the agenda for today’s tiger team call:


-  ONAP Microservices Architecture for Casablanca and beyond

Please share your slides prior to the call. I hope Manoj, Alex, Manish and 
other folks who have been quite active in driving this work in ONAP can join 
the call as well.


Thank you


Parviz


 


---


PARVIZ YEGANI, PhD 
Chief SDN/NFV Architect


CTO Office, Cloud Network Solutions


 


FutureWei Technologies, Inc.


2330 Central Express Way


Santa Clara, CA 95050, USA


Phone: +1 (408) 330-4668


Mobile : +1 (408) 759-1973


parviz.yeg...@huawei.com 


 


 


 


From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn] 
 Sent: Wednesday, March 14, 2018 4:01 AM
 To: Parviz Yegani ; Christopher Donley (Chris) 

 Cc: onap-arch-tiger-t...@lists.onap.org; onap-discuss@lists.onap.org
 Subject: Some thoughts about ONAP Microservice Architecture for Casablanca and 
beyond: Service Mesh, Centralized Authentication and unified API standards 


 

Hi all,

I'd like to share some of my thoughts about ONAP Microservice Architecture for 
Casablanca and beyond

 

1. Service Mesh

Service Mesh is the next generation of Microservice approach, which can bring 
lots of benefits to ONAP and its users at both the development and operation 
sides. Such as 


· the separation of business logic and Microservice 
infrastructure(communication, security, metrics etc)


· allowing free choice of development tech stack


· flexible route rules to enable traffic steering and canary release


· monitoring and tracing visibility


· fault injection for resiliency testing, etc

We should take service mesh into consideration. There are multiple choices on 
the table right now, given its tight relationship with kubernetes which is used 
for ONAP deployment, I suggest we give Istio a shot in Casablanca. MSB project 
is investigating  the possibility of integration of Istio and ONAP right now. 

 

2. Centralized Authentication

ONAP is a huge system consisting of many services. Currently, different 
services such as AAI, SDC, Policy etc. have their own authentication process, 
which makes ONAP difficult to use and adds burden to the individual project to 
enforce the cross-project  authentication logic. We need to consider 
implementing some kind of centralized authentication, which means user login 
once and can access all the services. We also need to consider how to secure 
the access of 3-party systems by using API token or OAuth.

 

3. Unified API standard

Most of the projects produce RESTFul APIs for consuming, but in a 
none-consistent way. we need to define some unified standards/best practices on 
the REST API definition across the ONAP projects such as versioning, url, error 
code.  There is a draft in the  wiki page: 
https://wiki.onap.org/display/DW/RESTful+API+Design+Specification

BR,

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

Re: [onap-discuss] Some thoughts about ONAPMicroserviceArchitecturefor Casablanca and beyond: Service Mesh,CentralizedAuthentication and unified API standards

[zhao.huabing]

Hi Tal,



You make a very good point! The current name MSB(Microservices Bus) can't well 
explain the project anymore, we're considering to change to a new name which 
can better reflect the scope and functionalities. 


But I don't know if it's appropriate to call it service mesh only, service mesh 
definitely is part of it and will be the focus in the foreseeable future, but 
Microservices Architecture includes a number of things, for example, I think 
the API Gateway may not be part of service mesh.


How about we come up with a more general name?


BR,


Huabing



原始邮件



发件人：TalLiron 
收件人：onap-discuss@lists.onap.org 
日 期 ：2018年03月16日 03:39
主 题 ：Re: [onap-discuss] Some thoughts about ONAPMicroserviceArchitecturefor 
Casablanca and beyond: Service Mesh,CentralizedAuthentication and unified API 
standards


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


Or perhaps just "Service Mesh" (SM) project.___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Some thoughts about ONAPMicroserviceArchitecture for Casablanca and beyond: Service Mesh,CentralizedAuthentication and unified API standards

[zhao.huabing]

Hi Srini,


Yes, that's the idea and welcome onboard!


We are planning to give a demo to show the benefits of Istio can bring in to 
ONAP such as visibility, routing rule and mutal tls, etc. There is no fixed day 
yet, probably at the end of Beijing and the planning phase of Casablanca.


BR,


Huabing







原始邮件



发件人：Addepalli,SrinivasaR 
收件人：赵化冰10201488;tli...@redhat.com 
抄送人：onap-discuss@lists.onap.org 
日 期 ：2018年03月14日 23:09
主 题 ：RE: [onap-discuss] Some thoughts about ONAPMicroserviceArchitecture for 
Casablanca and beyond: Service Mesh,CentralizedAuthentication and unified API 
standards




Hi Huabing,


 


I agree with you service mesh technologies are best as it takes away majority 
of housekeeping work away from the ONAP service developers – Authenticating 
peers,  Authorization of peers requests,  Secure communication (Mutual TLS),  
visibility and more.


 


Great that you intend to show istio demo. 


 


I guess istio.io CA for certificate enrollment will be used and ENVOY proxy for 
Mutual TLS endpoint will be leveraged. In security project, we are also 
thinking  of enabling isito.io CA (some modifications are needed) to take 
advantage of HSMs and also providing CA keys security rooted in HW. 


 


When are you planning to show the demo? 


 


Thanks


Srini


 


 


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhao.huab...@zte.com.cn
 Sent: Wednesday, March 14, 2018 1:26 AM
 To: tli...@redhat.com
 Cc: onap-discuss@lists.onap.org
 Subject: Re: [onap-discuss] Some thoughts about ONAP MicroserviceArchitecture 
for Casablanca and beyond: Service Mesh,Centralized Authentication and unified 
API standards


 

Hi Tal,

Good points.


1. You're right, Istio is still not production ready while service mesh 
approach is very promising, We're trying to set up a demo with ONAP to 
demonstrate its benefits.  


2. I agree that most of the APIs we have now are not "REST", actually 
sometimes it's difficult to make the HTTP APIs "100%" REST, but we still need a 
standard for all  the "HTTP" or "REST-like" APIs to make the APIs more friendly 
for the ONAP developers and users. Just feel free to edit the wiki page, it's 
an input for improvement:-).

BR,

Huabing


原始邮件



发件人：TalLiron 



收件人：onap-discuss@lists.onap.org 



日 期 ：2018年03月14日 14:06



主 题 ：Re: [onap-discuss] Some thoughts about ONAP MicroserviceArchitecture for 
Casablanca and beyond: Service Mesh,Centralized Authentication and unified API 
standards




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


Hi Huabing,



1.
 
We have some good experience with Itsio and would love to be part of the 
conversation. It's one of the things we're looking at, too, in terms of 
improving ONAP's currently basic containerization. We are starting by looking 
at OOM but hope to find best practices  that could work for all projects. I 
think it's better to convince with a PoC rather than theory in this case, 
because Itsio is indeed quite new, sometimes hard to explain, but its benefits 
are clear when you see them in use.



3.
 
In terms of our "RESTful" APIs -- this has been a pet peeve of mine for a long 
time, but I wish we would stop calling all our APIs RESTful, when in fact they 
are rarely RESTful in our project. They are simply "HTTP" (or "web") APIs. 
"CRUD" does not map very  well onto REST. That said, I applaud your proposal 
and it has many good points. But I would like to make a few comments:
 
I would add this emphasis: readers should pay attention to the use of POST for 
"create". I've seen many frameworks recommend PUT for "create", which is 
definitely wrong (not exactly: more on that below). POST is the only 
non-idempotent HTTP verb, and as such  will guarantee atomicity: the resource 
will not be created twice, even being a proxy.



However, using PUT for "update" is imprecise. Especially your comment that if 
the resource does not exist then PUT would return an error. Here is the 
description of PUT from the HTTP spec:
 
"The PUT method requests that the enclosed entity be stored under the
supplied Request-URI. If the Request-URI refers to an alreadyexisting 
resource, the enclosed entity SHOULD be considered as amodified version of 
the one residing on the origin  server. If theRequest-URI does not point to 
an existing resource, and that URI iscapable of being defined as a new 
resource by the requesting useragent, the origin server can create the 
resource with that URI. If anew resource is created, the  origin server 
MUST inform the user agentvia the 201 (Created) response."



So, as you see, PUT is also a kind of "create". But because PUT is idempotent, 
you definitely don't want to 

Re: [onap-discuss] Some thoughts about ONAP MicroserviceArchitecture for Casablanca and beyond: Service Mesh,Centralized Authentication and unified API standards

[zhao.huabing]

Hi Tal,



Good points.


You're right, Istio is still not production ready while service mesh approach 
is very promising, We're trying to set up a demo with ONAP to demonstrate its 
benefits.  


I agree that most of the APIs we have now are not "REST", actually sometimes 
it's difficult to make the HTTP APIs "100%" REST, but we still need a standard 
for all the "HTTP" or "REST-like" APIs to make the APIs more friendly for the 
ONAP developers and users. Just feel free to edit the wiki page, it's an input 
for improvement:-).


BR,


Huabing



原始邮件



发件人：TalLiron 
收件人：onap-discuss@lists.onap.org 
日 期 ：2018年03月14日 14:06
主 题 ：Re: [onap-discuss] Some thoughts about ONAP MicroserviceArchitecture for 
Casablanca and beyond: Service Mesh,Centralized Authentication and unified API 
standards


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


Hi Huabing,


1.

We have some good experience with Itsio and would love to be part of the 
conversation. It's one of the things we're looking at, too, in terms of 
improving ONAP's currently basic containerization. We are starting by looking 
at OOM but hope to find best practices that could work for all projects. I 
think it's better to convince with a PoC rather than theory in this case, 
because Itsio is indeed quite new, sometimes hard to explain, but its benefits 
are clear when you see them in use.


3.

In terms of our "RESTful" APIs -- this has been a pet peeve of mine for a long 
time, but I wish we would stop calling all our APIs RESTful, when in fact they 
are rarely RESTful in our project. They are simply "HTTP" (or "web") APIs. 
"CRUD" does not map very well onto REST. That said, I applaud your proposal and 
it has many good points. But I would like to make a few comments:

I would add this emphasis: readers should pay attention to the use of POST for 
"create". I've seen many frameworks recommend PUT for "create", which is 
definitely wrong (not exactly: more on that below). POST is the only 
non-idempotent HTTP verb, and as such will guarantee atomicity: the resource 
will not be created twice, even being a proxy.


However, using PUT for "update" is imprecise. Especially your comment that if 
the resource does not exist then PUT would return an error. Here is the 
description of PUT from the HTTP spec:

"The PUT method requests that the enclosed entity be stored under the
supplied Request-URI. If the Request-URI refers to an alreadyexisting 
resource, the enclosed entity SHOULD be considered as amodified version of 
the one residing on the origin server. If theRequest-URI does not point to 
an existing resource, and that URI iscapable of being defined as a new 
resource by the requesting useragent, the origin server can create the 
resource with that URI. If anew resource is created, the origin server MUST 
inform the user agentvia the 201 (Created) response."


So, as you see, PUT is also a kind of "create". But because PUT is idempotent, 
you definitely don't want to support PUT on "/pets/dogs". But PUT on 
"/pets/dogs/bailey" should work. (Even if the request is sent several times, it 
would create/update the same resource, so idempotency is honored).


What does it mean that there are two ways to "create" the resource? Actually, 
they are different. When you POST to "/pets/dogs" you do not yet know the ID of 
the dog. The ID would be created for you (once and only once) and returned in 
the response. However, in some cases you know in advance the ID of the object, 
in which case you should PUT to "/pets/dogs/ID". Then, you would know if it was 
created by checking the status code: 200 for modified or 201 for created. 
(Though note that it's not a good idea to functionally rely on this 
distinction: because PUT is idempotent, there is a chance that more than one 
client would get the 201 response in the case of caching proxies.)


As for APIs that are not CRUD-like, it's important for the designer to think 
twice before using POST, because POST is the least scalable verb (it can never 
be cached). Ask yourself: what would happen if the API got called more than 
once with exactly the same request content? If the answer is "bad things", then 
definitely use POST. (All classic RPC-like "function calls" on web APIs should 
basically use POST.) For all other cases, use PUT or GET as appropriate.


Finally, for your section on HTTP status codes, I would add this emphasis: make 
sure never to return 2XX series success codes in case of an error. I've seen 
APIs return 200 with an error code inside the JSON response. This makes 
exception handling on the client side inconsistent and can lead to bugs.


If we want to do this right, I would go even further and make sure to 1) return 
client caching headers (maxAge, etag, etc.) with every response where 
appropriate, and 2) try 

[onap-discuss] Some thoughts about ONAP Microservice Architecture for Casablanca and beyond: Service Mesh, Centralized Authentication and unified API standards

[zhao.huabing]

Hi all,


I'd like to share some of my thoughts about ONAP Microservice Architecture for 
Casablanca and beyond




1. Service Mesh


Service Mesh is the next generation of Microservice approach, which can bring 
lots of benefits to ONAP and its users at both the development and operation 
sides. Such as 

the separation of business logic and Microservice infrastructure(communication, 
security, metrics etc)

allowing free choice of development tech stack

flexible route rules to enable traffic steering and canary release

monitoring and tracing visibility

fault injection for resiliency testing, etc

We should take service mesh into consideration. There are multiple choices on 
the table right now, given its tight relationship with kubernetes which is used 
for ONAP deployment, I suggest we give Istio a shot in Casablanca. MSB project 
is investigating the possibility of integration of Istio and ONAP right now. 




2. Centralized Authentication

ONAP is a huge system consisting of many services. Currently, different 
services such as AAI, SDC, Policy etc. have their own authentication process, 
which makes ONAP difficult to use and adds burden to the individual project to 
enforce the cross-project authentication logic. We need to consider 
implementing some kind of centralized authentication, which means user login 
once and can access all the services. We also need to consider how to secure 
the access of 3-party systems by using API token or OAuth.




3. Unified API standard

Most of the projects produce RESTFul APIs for consuming, but in a 
none-consistent way. we need to define some unified standards/best practices on 
the REST API definition across the ONAP projects such as versioning, url, error 
code.  There is a draft in the wiki page: 
https://wiki.onap.org/display/DW/RESTful+API+Design+Specification



BR,

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

[onap-discuss] 答复: RE: Re: MSB upgrade

[zhao.huabing]

Hi Pavithra,


It seems that ESR has problem accessing AAI via msb api gateway, but we can't 
reproduce this issue in our local environment.  So could you please try to 
access aai via the node port of MSB?  Such as 
http://127.0.0.1:30080/api/aai-externalSystem/v11/esr-vnfm-list/esr-vnf/ and 
then send me the log of msb internal api gateway? It will be better if you can 
try to access aai directly first to check if aai works.






If you want to reinstall msb, after that, please restart kub2msb after that, 
the all services can be registered to the new msb instance automatically. We 
don't need to manually register the services.






Thanks,


Huabing







原始邮件



发件人：PavithraR13 
收件人：赵化冰10201488;李滋00164331;
抄送人：onap-discuss@lists.onap.org 
日 期 ：2018年02月28日 15:19
主 题 ：RE: Re: [onap-discuss] MSB upgrade




Hi Zhao


 


I am able to access ESR via MSB port , but the vnfm and vim is not getting 
registered. I could see “Bad Gateway Error” during registration. PFA screenshot 
for  the error in log.


 


Lizi/Zhao,


 


We would like to reinstall only MSB without disturbing the other services. In 
that case will already installed services be registered in MSB automatically, 
or  it will require manual registration with MSB.


 


Regards


Pavithra R


 



From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn] 
 Sent: Wednesday, February 28, 2018 12:18 PM
 To: li.z...@zte.com.cn; Pavithra R13 
 Cc: onap-discuss@lists.onap.org
 Subject: Re: Re: [onap-discuss] MSB upgrade




 



This message was identified as a phishing scam.



Feedback

Hi Pavithra, Lizi,

 

We don't have to manually unregister and register services in OOM/k8s 
deployment. Kube2msb is watching the k8s deployment change events and 
automatically register/unregister services to MSB.

 

"UUI/ESR is not able to communicate with AAI through MSB"

 

Are you able to access ESR via the node port of MSB?  Such as 
http://127.0.0.1:30080/iui/aai-esr-gui/extsys/vim/vimView.html


If IIf you get problem accessing it, please send me log of msb internal api 
gateway. You can get the log by run: docker logs {contianer_id_of_msb-iag}

 

Thanks,

Huabing


原始邮件



发件人：李滋00164331



收件人：pavithra_...@infosys.com 



抄送人：onap-discuss@lists.onap.org 



日 期 ：2018年02月28日 14:31



主 题 ：Re: [onap-discuss] MSB upgrade




___
onap-discuss mailing list
 onap-discuss@lists.onap.org
 
https://imsva91-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.onap.org%2fmailman%2flistinfo%2fonap%2ddiscuss=3DC9A076-6640-2905-A1C6-28406BBF484C=f63efd9aed1e0a367f4bd39381444e47841a5725-653f35cfe3bf0555a380bcd03eede5ad37283ed1

Hi Pavithra R,

 

You can just delete the register information from msb portal, and re-register 
the service to MSB. Please refer to the curl commond in 
https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=boot/msb_vm_init.sh;h=0a087b04bdaa8dc9b534ffe28673dd3e81a7e428;hb=HEAD
 .  You not have to reinstall MSB or the other services.

 

For MSB portal please visit http://MSB_IP/iui/microservices/default.html . 
Click the msdiscover card. There will be a  swagger ui under that page. Call 
the API to delete the register information.

DELETE /services/{serviceName}/version/{version}  

Thanks,

LiZi

 

 






发件人：PavithraR13 



收件人：onap-discuss@lists.onap.org 



日 期 ：2018年02月28日 13:43



主 题 ：[onap-discuss]  MSB upgrade




___
onap-discuss mailing list
 onap-discuss@lists.onap.org
 
https://imsva91-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.onap.org%2fmailman%2flistinfo%2fonap%2ddiscuss=3DC9A076-6640-2905-A1C6-28406BBF484C=f63efd9aed1e0a367f4bd39381444e47841a5725-653f35cfe3bf0555a380bcd03eede5ad37283ed1
 
 


Hi All


 


We have currently installed Kubernetes based ONAP Amsterdam on our environment. 
We need few clarifications regarding MSB.


 


1.   UUI/ESR is not able to communicate with AAI through MSB, but all 
corresponding services are registered with MSB. What could be the issue?


2.   We would like to upgrade MSB image to latest version. In that case 
should we re-install all the other components so that it will be registered 
with MSB or is there any other procedure to register the components with MSB 
without re-installation?


 


Regards


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

Re: [onap-discuss] MSB upgrade

[zhao.huabing]

Hi Pavithra, Lizi,






We don't have to manually unregister and register services in OOM/k8s 
deployment. Kube2msb is watching the k8s deployment change events and 
automatically register/unregister services to MSB.






"UUI/ESR is not able to communicate with AAI through MSB"






Are you able to access ESR via the node port of MSB?  Such as 
http://127.0.0.1:30080/iui/aai-esr-gui/extsys/vim/vimView.html



If IIf you get problem accessing it, please send me log of msb internal api 
gateway. You can get the log by run: docker logs {contianer_id_of_msb-iag}






Thanks,


Huabing



原始邮件



发件人：李滋00164331
收件人：pavithra_...@infosys.com 
抄送人：onap-discuss@lists.onap.org 
日 期 ：2018年02月28日 14:31
主 题 ：Re: [onap-discuss] MSB upgrade


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



Hi Pavithra R,






You can just delete the register information from msb portal, and re-register 
the service to MSB. Please refer to the curl commond in 
https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=boot/msb_vm_init.sh;h=0a087b04bdaa8dc9b534ffe28673dd3e81a7e428;hb=HEAD
 . You not have to reinstall MSB or the other services.






For MSB portal please visit http://MSB_IP/iui/microservices/default.html . 
Click the msdiscover card. There will be a swagger ui under that page. Call the 
API to delete the register information.

DELETE /services/{serviceName}/version/{version} 




Thanks,


LiZi














发件人：PavithraR13 
收件人：onap-discuss@lists.onap.org 
日 期 ：2018年02月28日 13:43
主 题 ：[onap-discuss]  MSB upgrade


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

 

Hi All


 


We have currently installed Kubernetes based ONAP Amsterdam on our environment. 
We need few clarifications regarding MSB.


 


1.   UUI/ESR is not able to communicate with AAI through MSB, but all 
corresponding services are registered with MSB. What could be the issue?


2.   We would like to upgrade MSB image to latest version. In that case 
should we re-install all the other components so that it will be registered 
with MSB or is there any other procedure to register the components with MSB 
without re-installation?


 


Regards


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

Re: [onap-discuss] [integration] Intel lab network error

[zhao.huabing]

Hi Stephen,







The MSB(Microservices) project at the Intel open lab has the same issue. All 
IPs of the VM are lost on the instances page of management UI. Is it possible 
to fix it, or we should recreate all the VMs?






Thanks,


Huabing







原始邮件



发件人：Gooch,Stephen 
收件人：Gary Wu Yang Xu (Yang, Fixed Network) 
Michael O'Brien 
抄送人：onap-discuss 
日 期 ：2018年02月15日 04:57
主 题 ：Re: [onap-discuss] [integration] Intel lab network error


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

 

Hi Gary,


 


User demo was only admin in SB-00, this is no longer the case.   demo is now a 
normal user in SB_00 as it is in the other integration projects.


 


Br,


- Stephen


 



From: Gooch, Stephen 
 Sent: Wednesday, February 14, 2018 15:39
 To: 'Gary Wu'; 'Yang Xu (Yang, Fixed Network)'; 'Michael O'Brien'
 Cc: 'onap-discuss'
 Subject: RE: [integration] Intel lab network error




 


FYI:


 


The following was called to reconnect the jumpstation:


 


wruser@tacit:~/windriver/TiC/ONAP$ os network list | grep admin


| 48573914-055a-4b8d-b03c-66c291170757 | admin-mgmt 
   | 807ea269-0ff1-4a25-95f3-702d13882be6 |


wruser@tacit:~/windriver/TiC/ONAP$ os server list


+--+++--++


| ID   | Name   | Status | Networks 
| Image Name |


+--+++--++


| fd59c968-8125-4a5a-9b54-7effd16828e6 | vBoothost  | ACTIVE |  
||


| b9dd852f-4b5c-4432-a721-108c833c27ac | POD-ONAP-01-vJhost | ACTIVE |  
||


+--+++--++


wruser@tacit:~/windriver/TiC/ONAP$ nova interface-attach --net-id 
48573914-055a-4b8d-b03c-66c291170757 b9dd852f-4b5c-4432-a721-108c833c27ac


wruser@tacit:~/windriver/TiC/ONAP$ nova interface-attach --net-id 
48573914-055a-4b8d-b03c-66c291170757 fd59c968-8125-4a5a-9b54-7effd16828e6


 


A new Neutron router was added between the admin-mgnt tenant network and the 
external network.   Then a floating IP was re-requested.


The new floating IP for the jumpstation is 10.12.5.50. Thus, it is easy  
enough to reconnect an individual VM, but for the stacks, I’d assume one would 
delete them and start over.


 


Assuming user “demo” was used, I am checking to see if this user is admin in 
any other projects other than SB-02.  And then removing Admin privilege.  


 


Br,


- Stephen


 



From: Gooch, Stephen 
 Sent: Wednesday, February 14, 2018 15:13
 To: 'Gary Wu'; Yang Xu (Yang, Fixed Network); Michael O'Brien
 Cc: onap-discuss
 Subject: RE: [integration] Intel lab network error




 


Hi Gary,


 


In SB-00 most users are normal users.  The following are ADMIN:


 


Helen, Marco and demo


 


In SB02


Helen and Marco are still admins, but demo is not.  Where you running as the 
demo user in SB-00?


 


Br,


- Stephen


 



From: Gary Wu [mailto:gary.i...@huawei.com] 
 Sent: Wednesday, February 14, 2018 15:03
 To: Gooch, Stephen; Yang Xu (Yang, Fixed Network); Michael O'Brien
 Cc: onap-discuss
 Subject: RE: [integration] Intel lab network error




 


Hi Stephen,


 


It looks like the cleanup scripts that deletes all floating IPs and routers 
within a tenant, when run from the Integration-SB-00 tenant, somehow managed to 
delete all of them across the Integration-* tenants  (and maybe others?).


 


This does not happen when running the cleanup scripts from any other 
Integration-* tenants such as Integration-SB-02 or Integration-Jenkins.


 


Does the SB-00 tenant have some special cross-tenant permissions?


 


Thanks,


Gary


 



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gooch, Stephen
 Sent: Wednesday, February 14, 2018 11:54 AM
 To: Yang Xu (Yang, Fixed Network) 
 Cc: onap-discuss 
 Subject: Re: [onap-discuss] [integration] Intel lab network error




 


HI Gary,


 


It appears the all the Neutron routers have been deleted from the cloud.   And 
the VM interfaces along with it.   I’ll recreate the admin Neutron router and 
re-connect the jump station; then get back to you.


 


- Stephen


 



From: Yang Xu (Yang, Fixed Network) [mailto:yang@huawei.com] 
 Sent: Wednesday, February 14, 2018 14:40
 To: Gooch, Stephen
 Cc: onap-discuss
 Subject: [integration] Intel lab network error




 


Stephen,


 


I can’t access any VM public IP in Intel lab now. Is there any issue in the 
network?


 


Thanks,


-Yang___
onap-discuss 

[onap-discuss] 答复: RE: [OOM][MSB] Kube2MSB RBAC security issues

[zhao.huabing]

Hi Nicolas,


Thanks for looking into this issue and solve it!


It looks to me that the second is more elegant.


BR,


Huabing



原始邮件



发件人： ;
收件人： ; ;赵化冰10201488;
日 期 ：2018年02月02日 03:01
主 题 ：RE: [OOM][MSB] Kube2MSB RBAC security issues




Hi Michael , Huabing


 


Here is the reason why Kube2MSB failed in RBAC enabled cluster.


 


The kube2MSB  will use the token from service account kube-system:default. This 
service account doesn’t have the admin privileges.


 


To fix that issue there are 2 ways


 


1.   Create a clusterrolebinding assign admin privileges to that service 
account


 


Just run following command:


kubectl create clusterrolebinding kube-system-default-admin-binding 
--clusterrole=cluster-admin --serviceaccount=kube-system:default


 


This command should execute once. Should we put it in 
createConfig.sh  ?


 


2.   Instead of using token from service account kube-system:default,  
kube2msb can use the token form service account onap-kube2msb:default .


In createAll.bash  the ClusterRoleBinding is created for onap-kube2msb:default. 
So that account already get the admin privileges.


 


Change the kube-system to $1-$2


 


   87   # assign default auth token


   88   if [[ -z $ONAP_DEFAULT_AUTH_TOKEN ]]; then


   89 DEFAULT_SECRET=`kubectl get secrets -n kube-system | grep 
default-token |  awk '{ print $1}'`


   90 ONAP_DEFAULT_AUTH_TOKEN=`kubectl get secrets $DEFAULT_SECRET -n 
kube-system -o yaml | grep  'token:'  | awk '{ print $2}' | base64 --decode`


   91   fi


   92 


  93cmd=`echo helm install $LOCATION/$2/ --name $1-$2 --namespace $1 --set 
nsPrefix=$1,nodePortPrefix=$3,kubeMasterAuthToken=$ONAP_DEFAULT_AUTH_TOKEN 
${HELM_VALUES_ADDITION}`


   94   eval ${cmd}


   95   check_return_code $cmd


 


Thanks,


Nicolas


 


[centos@server-186-kubernetes-master-host-8z2tnf robot]$ kubectl get 
ClusterRoleBinding onap-kube2msb-admin-binding -o yaml


apiVersion: rbac.authorization.k8s.io/v1


kind: ClusterRoleBinding


metadata:


  creationTimestamp: 2018-01-30T20:18:49Z


  name: onap-kube2msb-admin-binding


  resourceVersion: "159146"


  selfLink: 
/apis/rbac.authorization.k8s.io/v1/clusterrolebindings/onap-kube2msb-admin-binding


  uid: c838ff8d-05fa-11e8-bad9-fa163efe5022


roleRef:


  apiGroup: rbac.authorization.k8s.io


  kind: ClusterRole


  name: cluster-admin


subjects:


- kind: ServiceAccount


  name: default


  namespace: onap-kube2msb


 


 



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of HU, JUN NICOLAS
 Sent: Wednesday, January 31, 2018 12:06 PM
 To: OBRIEN, FRANK MICHAEL ; 
onap-discuss@lists.onap.org
 Subject: [onap-discuss] [OOM][MSB] Kube2MSB RBAC security issues




 


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


Hi,


 


I created https://jira.onap.org/browse/OOM-645.


 


The Kube2MSB cannot access the apis of pods and services.


 


Thanks,


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

[onap-discuss] 答复: Re: VIM registration failure

[zhao.huabing]

Hi Kiruthiga,


Could you please get log of MSB internal api gateway using "sudo docker logs "? 
 It may help to investigate this issue.






Thanks,


Huabing











原始邮件



发件人： ;
收件人：李滋00164331;
抄送人： ;
日 期 ：2018年02月01日 19:45
主 题 ：Re: [onap-discuss] VIM registration failure


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

 

Hi LiZi,


 


Both AAI and Multicloud services are registered in MSB. But still we are 
getting the same error mentioned in the below mail.


 


All the request to MSB API is resulting in “Bad Gateway error”.  The external 
port of MSB-IAG server is either in CLOSE_WAIT or TIME_WAIT status while 
triggering  MSB API calls. If you could see in the error screenshot, during VIM 
registration request is sent to MSB-IAG server and it gives “Bad Gateway 
error”. Please help in fixing this issue.


 


Regards,


Kiruthiga



 



From: li.z...@zte.com.cn [mailto:li.z...@zte.com.cn] 
 Sent: Thursday, February 1, 2018 4:36 PM
 To: Kiruthiga R 
 Cc: onap-discuss@lists.onap.org
 Subject: Re: [onap-discuss] VIM registration failure




 



This message was identified as a phishing scam.



Feedback

Hi Kiruthiga,

Before you register VIM with ESR GUI, you need register the AAI's service to 
MSB. Also, you need register Multi-Cloud to MSB. You may check the registration 
result with MSB GUI (http://MSB_SERVER_IP/iui/microservices/default.html).  If 
they are not registered, please register with the following command.

 

curl -X POST \

-H "Content-Type: application/json" \

-d '{"serviceName": "aai-cloudInfrastructure", "version": "v11", "url": 
"/aai/v11/cloud-infrastructure","protocol": "REST", "enable_ssl":"true", 
"visualRange":"1", "nodes": [ {"ip": "ESR_SERVER_IP","port": "8443"}]}' \

http://MSB_SERVER_IP:10081/api/microservices/v1/services 

 

curl -X POST -H “Content-Type: application/json” -d ‘{“serviceName”: 
“multicloud”, “version”: “v0”, “url”: “/api/multicloud/v0”,”protocol”: “REST”, 
“nodes”: [ {“ip”: “’$MultiCloud_IP’”,”port”: “9001”}]}’ 
“http://$MSB_SERVER_IP:10081/api/microservices/v1/services“ 

 

Thanks,

LiZi

 

 


原始邮件



发件人： ;



收件人： ;



日 期 ：2018年02月01日 17:55



主 题 ：[onap-discuss]  VIM registration failure




___
onap-discuss mailing list
 onap-discuss@lists.onap.org
 
https://imsva91-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.onap.org%2fmailman%2flistinfo%2fonap%2ddiscuss=CAD20441-6424-9305-A7AC-9253E32E6B5F=f63efd9aed1e0a367f4bd39381444e47841a5725-599b5ddaa682f840307a6cbf4482e982d884cbe8
 
 


Hi Team,


 


We have installed Amsterdam release of ONAP. We were successfully able to 
demonstrate vFW heat template based instantiation. We are currently working on 
TOSCA based E2E service  instantiation. We have a customer vCER CSAR file with 
which  we were able to create and distribute network and E2E service. We were 
able to onboard vnf and ns packages using usecase-UI. While trying to do VIM 
registration through ESR GUI, we are facing ExtsysException: PUT cloud region 
to AAI failed. When we tried to debug, all request to MSB-IAG is resulting “Bad 
Gateway”.


 



 
 
 


The external port getting exposed to msb-iag is in CLOSE_WAIT state. Please 
help in resolving the port issue and to proceed VIM registration.


 


Regards,


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

[onap-discuss] 答复: time of SDC Team ONAP4 weekly meeting

[zhao.huabing]

Hi Liang,


It seems that the SDC weekly meeting is now held between 11pm and 12pm China 
Time.






You may subscribe the ONAP google calendar so you always get the latest update 
of the meeting schedules.


https://calendar.google.com/calendar/embed?src=linuxfoundation.org_1rmtb5tpr3uc8f76fmflploi88%40group.calendar.google.com=Asia%2FShanghai
 


or iCal format:


https://calendar.google.com/calendar/ical/linuxfoundation.org_1rmtb5tpr3uc8f76fmflploi88%40group.calendar.google.com/public/basic.ics







Mon, February 5, 11pm – Tue, February 6, 12am
Weekly on Monday







https://zoom.us/j/489989304







2 guests
2 awaiting









ml6...@intl.att.com







onap-discuss









Description:Hi there, 

ONAP Meeting 4 is inviting you to a scheduled Zoom meeting. 

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/489989304Or iPhone 
one-tap (US Toll):  +14086380968,,489989304# or +16465588656,,489989304#

Or Telephone:
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
+1 855 880 1246 (US Toll Free)
+1 877 369 0926 (US Toll Free)
Meeting ID: 489 989 304
International numbers available: 
https://zoom.us/zoomconference?m=aBHgZkfSu_j-URGxXCTMLZ2_0FUeopNH



















原始邮件



发件人： ;
收件人： ;
日 期 ：2018年01月31日 00:30
主 题 ：[onap-discuss] time of SDC Team ONAP4 weekly meeting


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

 

Hi, All


 


I’d like to participate the weekly meeting of SDC, however, it seems that the 
time of this meeting


is not 10pm for china any more. It may be changed but the wiki page 
(https://wiki.onap.org/pages/viewpage.action?pageId=8230628)


may not be updated, could you please tell me the updated weekly meeting time of 
SDC. Appreciate that!


 


 


B.R.


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

Re: [onap-discuss] [onap-tsc] CII Badging Attention PTL

[zhao.huabing]

Thanks, Arul!











Original Mail



Sender:  ;
To: zhaohuabing10201488; ; ;
CC:  ; ; 
; ;
Date: 2018/01/26 22:34
Subject: RE: [onap-discuss] [onap-tsc] CII Badging Attention PTL 




Hi Huabing,


In your case the report will be for msb project.


So your project home page URL will be


https://wiki.onap.org/display/DW/Microservices+Bus+Project


 


And your gerrit repo URL will be


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


 


Currently in my testing linux foundation does not allow us to clone under 
project level. We will have to talk to CII badging to see if the URL needs to 
be useable  or is it only for reference. If it has to be usable link then we 
will have to ask Linux foundation to let us clone a full project instead of a 
repo.


Hope this helps.


Regards


Arul


 


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhao.huab...@zte.com.cn
 Sent: Thursday, January 25, 2018 8:32 PM
 To: t...@att.com; stephen.terr...@ericsson.com
 Cc: onap-sec...@lists.onap.org; Rajeev Mehta ; 
onap-discuss@lists.onap.org; onap-...@lists.onap.org
 Subject: Re: [onap-discuss] [onap-tsc] CII Badging Attention PTL 


 

Hi Tony, Steve,

Thanks for the explanation, it really helped. 

One more question, do you happend to know how could I submit all the repos 
together if I want to apply at project level? 

The below screenshot show that only one repo can be submitted per project. I 
tried to contact Core Infrastructure Initiative directly to get the answer, but 
I can't find their contact information.



 

Thanks,

Huabing

 

 


Original Mail



Sender:  ;



To: zhaohuabing10201488;



CC:  ; ; 
;  ; 
;



Date: 2018/01/25 22:54



Subject: Re: [onap-discuss] [onap-tsc] CII Badging Attention PTL




As PTL, it’s your choice. You can do a single report for your entire project, 
or you can file a separate report for each repo. If your repos use different 
languages or different  testing procedures, you probably would find it easier 
to do  it per-repo.


 


If you do file one report for the entire project, then you need to answer each 
Met/Not Met question based on the lowest-common denominator answer: if any of 
the repos don’t meet  the requirement, you cannot select Met. (Use the text box 
 to keep track of your reasons for picking any particular answer.)


 


Tony Hansen


 



From:  on behalf of 
"zhao.huab...@zte.com.cn" 
 Date: Thursday, January 25, 2018 at 2:16 AM
 To: "stephen.terr...@ericsson.com" 
 Cc: "onap-sec...@lists.onap.org" , 
"rajee...@amdocs.com" ,  "onap-discuss@lists.onap.org" 
, "onap-...@lists.onap.org" 

 Subject: Re: [onap-discuss] [onap-tsc] CII Badging Attention PTL



 

Hi Arul and Seve,

 

It's a common situation that an ONAP project has multiple repos. Is it possible 
to submit the rpos as a whole as one project when applying for CII  Badging? Or 
I have to submit one by one?

 



 

Thanks,

Huabing


Original Mail



Sender:  ;



To:  ;  ;  
; ;



CC:  ;



Date: 2018/01/25 00:27



Subject: Re: [onap-tsc] CII Badging Attention PTL




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


Hi,


 


Thanks to Arul and team for putting this together.


 


We had one clarification today in the security subcommittee due to that it is 
discussed whether to do the badging at the project level  of the program level.


· In general it is fine (expected) to do this at the project level.


· However, a project may decide for different reasons to perform the 
badging per repo or set of repos; if this made sense.


· This would imply from a S3P tracking perspective


§  A project has passed if it and it its dependencies has passed.


§  Note: sub-projects are responsible for doing their own badging process.


§  For %complete the least complete value is the %complete of the project


BR,


 


Steve


 



From: Arul Nambi [mailto:arul.na...@amdocs.com] 
 Sent: 19 January 2018 20:23
 To: onap-discuss@lists.onap.org; onap-...@lists.onap.org; 
onap-sec...@lists.onap.org
 Cc: Stephen Terrill ; HANSEN, TONY L 
; Rajeev Mehta 
 Subject: CII Badging Attention 

[onap-discuss] Reply: [integration]Committers promotion for IntegrationProject: Eric Debeau

[zhao.huabing]

+1




Original Message



From:YunxiaChen;
To:wangchen...@chinamobile.com;dr6...@att.com;plata...@research.att.com;spondon...@att.com;yangyi@chinatelecom.cn;Gary
 Wu;Kang Xi;Yang Xu (Yang, 
FixedNetwork);lxin...@vmware.com;bin.y...@windriver.com;ran.pol...@amdocs.com;
Cc:onap-discuss;Eric Debeau;
Date:2018-01-26 23:10:47
Subject:[onap-discuss] [integration]Committers promotion for 
IntegrationProject: Eric Debeau


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

 
 
Dear Integration Committers,

 
 

 
I would like to propose to promote: Eric Debeau as the committer for 
Integration project. 

 
 

 
Eric has the expertise and background in integration; and he has made a lot of 
contributions in Integration project at Amsterdam release, mainly on:

 
1.   Integration documentation

 
2.   Integration testing at Orange open lab.

 
3.   Etc.

 
 

 
Git Commits: 62

 
Gerrit changesets: 50

 
Mailing Lists: 57

 
Jira: 21

 
(The above data is from ONAP Bitergia)

 
 

 
And he will continue contributing to documentation, ONAP maturity testing, ONAP 
“light” version, Benchmark project, etc.

 
 

 
Before I report this back to ONAP TSC / infrastructure coordinator, I would 
like to do an internal vote among all current Integration committers, which are 
on the “To” list:

 
1.   If you agree to promote Eric as committer of Integration project, 
please reply “+1”

 
2.   If you have no opinion, please reply “0”

 
3.   If you disagree to promote Eric as committer of Integration project, 
please reply “-1”

 
 

 
Please response before 6:00PM PST, 1/29/2018 (next Monday).

 
 

 
Regards,

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

Re: [onap-discuss] [onap-tsc] CII Badging Attention PTL

[zhao.huabing]

Hi Tony, Steve,

Thanks for the explanation, it really helped. 

One more question, do you happend to know how could I submit all the repos 
together if I want to apply at project level? 

The below screenshot show that only one repo can be submitted per project. I 
tried to contact Core Infrastructure Initiative directly to get the answer, but 
I can't find their contact information.









Thanks,


Huabing











Original Mail



Sender:  ;
To: zhaohuabing10201488;
CC:  ; ; 
; ; 
;
Date: 2018/01/25 22:54
Subject: Re: [onap-discuss] [onap-tsc] CII Badging Attention PTL




As PTL, it’s your choice. You can do a single report for your entire project, 
or you can file a separate report for each repo. If your repos use different 
languages or different testing procedures, you probably would find it easier to 
do  it per-repo.


 


If you do file one report for the entire project, then you need to answer each 
Met/Not Met question based on the lowest-common denominator answer: if any of 
the repos don’t meet the requirement, you cannot select Met. (Use the text box  
to keep track of your reasons for picking any particular answer.)


 


Tony Hansen


 



From:  on behalf of 
"zhao.huab...@zte.com.cn" 
 Date: Thursday, January 25, 2018 at 2:16 AM
 To: "stephen.terr...@ericsson.com" 
 Cc: "onap-sec...@lists.onap.org" , 
"rajee...@amdocs.com" , "onap-discuss@lists.onap.org" 
, "onap-...@lists.onap.org" 

 Subject: Re: [onap-discuss] [onap-tsc] CII Badging Attention PTL



 

Hi Arul and Seve,

 

It's a common situation that an ONAP project has multiple repos. Is it possible 
to submit the rpos as a whole as one project when applying for CII  Badging? Or 
I have to submit one by one?

 



 

Thanks,

Huabing


Original Mail



Sender:  ;



To:  ;  ; 
; ;



CC:  ;



Date: 2018/01/25 00:27



Subject: Re: [onap-tsc] CII Badging Attention PTL




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


Hi,


 


Thanks to Arul and team for putting this together.


 


We had one clarification today in the security subcommittee due to that it is 
discussed whether to do the badging at the project level  of the program level.

In general it is fine (expected) to do this at the project level.

However, a project may decide for different reasons to perform the badging per 
repo or set of repos; if this made sense.

This would imply from a S3P tracking perspective

A project has passed if it and it its dependencies has passed.

Note: sub-projects are responsible for doing their own badging process.

For %complete the least complete value is the %complete of the project


BR,


 


Steve


 



From: Arul Nambi [mailto:arul.na...@amdocs.com] 
 Sent: 19 January 2018 20:23
 To: onap-discuss@lists.onap.org; onap-...@lists.onap.org; 
onap-sec...@lists.onap.org
 Cc: Stephen Terrill ; HANSEN, TONY L 
; Rajeev Mehta 
 Subject: CII Badging Attention PTL




 


Hi Everyone,


If you have seen an email with almost the same subject ignore that, I had some 
issues posting the first email so I am re-sending it  again. Both emails have 
the same content


For getting ONAP carrier ready one of the requirements is that 70% of its 
projects needs to undergo a process called CII badging.


CII badging is a simple process(and takes less than a week normally) of 
answering some questions about the project. And it is better if you start it 
sooner than later.


And the security subcommittee has come up with a wiki page with

More information about the CII

Sample tools

Sample answers to all the questions that you will need to answer to get your 
app badged.


The current ask is that 70% of the project should be in passing level, if you 
want to go higher than that you can find the sample answers  for the Silver and 
gold level as well, they are not complete yet but if you find  answers then add 
them to the page.


Link: https://wiki.onap.org/display/DW/CII+Badging+Program


Let us know if you have any more questions or suggestions.


Regards


Arul


 


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

Re: [onap-discuss] [onap-tsc] CII Badging Attention PTL

[zhao.huabing]

Hi Arul and Seve,






It's a common situation that an ONAP project has multiple repos. Is it possible 
to submit the rpos as a whole as one project when applying for CII Badging? Or 
I have to submit one by one?














Thanks,


Huabing



Original Mail



Sender:  ;
To:  ; ; 
; ;
CC:  ;
Date: 2018/01/25 00:27
Subject: Re: [onap-tsc] CII Badging Attention PTL


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

  

Hi,


 


Thanks to Arul and team for putting this together.


 


We had one clarification today in the security subcommittee due to that it is 
discussed whether to do the badging at the project level of the program level.

In general it is fine (expected) to do this at the project level.

However, a project may decide for different reasons to perform the badging per 
repo or set of repos; if this made sense.

This would imply from a S3P tracking perspective

A project has passed if it and it its dependencies has passed.

Note: sub-projects are responsible for doing their own badging process.

For %complete the least complete value is the %complete of the project


BR,


 


Steve


 



From: Arul Nambi [mailto:arul.na...@amdocs.com] 
 Sent: 19 January 2018 20:23
 To: onap-discuss@lists.onap.org; onap-...@lists.onap.org; 
onap-sec...@lists.onap.org
 Cc: Stephen Terrill ; HANSEN, TONY L 
; Rajeev Mehta 
 Subject: CII Badging Attention PTL




 


Hi Everyone,


If you have seen an email with almost the same subject ignore that, I had some 
issues posting the first email so I am re-sending it again. Both emails have 
the same content


For getting ONAP carrier ready one of the requirements is that 70% of its 
projects needs to undergo a process called CII badging.


CII badging is a simple process(and takes less than a week normally) of 
answering some questions about the project. And it is better if you start it 
sooner than later.


And the security subcommittee has come up with a wiki page with

More information about the CII

Sample tools

Sample answers to all the questions that you will need to answer to get your 
app badged.


The current ask is that 70% of the project should be in passing level, if you 
want to go higher than that you can find the sample answers for the Silver and 
gold level as well, they are not complete yet but if you find  answers then add 
them to the page.


Link: https://wiki.onap.org/display/DW/CII+Badging+Program


Let us know if you have any more questions or suggestions.


Regards


Arul


 


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

[onap-discuss] Dual license dependencies reported by Nexus IQ - need help from LF legal experts

[zhao.huabing]

Hi there,







I noticed that some of the copyleft license policy violations reported by Nexus 
IQ are actually dual-licensed third-party dependecies. 


For example, the widely used jersey are dual-licensed - CDDL 1.1 and GPL 2.0 
with Class-path Exception and it says the downstream project can choose either 
one based on their requirements.






So my question is: can we use this kind of third-party dependencies in ONAP, or 
do I have to modify codes to avoid using any of these kinds of libs? 






Jersey license declaration on its github project page:

Licensing and Governance

Jersey is licensed under a dual license - CDDL 1.1 and GPL 2.0 with Class-path 
Exception. That means you can choose which one of the two suits your needs 
better and use it under those terms.






Thanks a lot,






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

Re: [onap-discuss] [ONAP Helpdesk #50378] Jenkins jobs failed (due to snapshot repository setting?)

[zhao.huabing]

OK.


Many thanks for your help.







Original Mail



Sender:  ;
To: zhaohuabing10201488;
CC:  ;
Date: 2018/01/19 06:10
Subject: [ONAP Helpdesk #50378] Jenkins jobs failed (due to snapshot repository 
setting?)


Closing this for now since the jobs have been removed in 
https://gerrit.onap.org/r/#/c/28373/

On Fri Jan 12 22:30:45 2018, zhao.huab...@zte.com.cn wrote:
> Hi Jess,
> 
> 
> 
> This failed project doesn't depend on any snapshot artifact of other
> projects.
> 
> 
> 
> 
> 
> For example, the failed job "msb-discovery-master-stage-site-java"
> says it can't find "org.onap.msb.discovery.sdclient:discovery-
> service:jar:1.1.0" which is an artifact generated by this maven
> project itself.
> 
> 
> 
> 
> I can find this artifact in the stagging and snapshot repo.
> 
> 
> 
> 
> 
> 
> 
> https://jenkins.onap.org/view/msb/job/msb-discovery-master-stage-site-
> java/
> 
> Build failed to find artifact
> org.onap.msb.discovery.sdclient:discovery-service:jar:1.1.0 needed for
> sub-project org.onap.msb.discovery.sdclient:discovery-
> standalone:pom:1.1.0. Check correct groupId, artifactId and version.
> This may also indicate a problem with nexus. Another possibility is
> that this is a -SNAPSHOT version and it has expired from nexus -- in
> that case check with the project which provides the artifact.
> 
> 
> 
> 
> Thanks,
> 
> 
> Huabing
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Original Mail
> 
> 
> 
> Sender:  ;
> To: zhaohuabing10201488;
> CC:  ;
> Date: 2018/01/04 09:15
> Subject: [ONAP Helpdesk #50378] Jenkins jobs failed (due to snapshot
> repository setting?)
> 
> 
> Although that can sound like the fastest way to fix it, is is best to
> move away from Snapshot dependencies as per these strategies:
> 
> https://wiki.onap.org/display/DW/Release+Versioning+Strategy#ReleaseVersioningStrategy-
> Whatarethe2bigissuestoaddress?
> 
> Thanks!
> Jess
> 
> On Tue Jan 02 22:01:53 2018, zhao.huab...@zte.com.cn wrote:
> > I mean, could we just use the snapshot artifacts for these Jenkins
> > jobs?
> >
> >
> > Before the release of 1.0.0, all jenkins jobs ran very well. Should I
> > modify these jobs or pom.xml to use snapshot instead of release?
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Original Mail
> >
> >
> >
> > Sender:  ;
> > To: zhaohuabing10201488;
> > CC:  ;
> > Date: 2018/01/03 10:04
> > Subject: [ONAP Helpdesk #50378] Jenkins jobs failed (due to snapshot
> > repository setting?)
> >
> >
> > We could point to an older released version of these artifacts.
> >
> > Also, if we decide to release this newer version 1.1.0 we won't be
> > putting it under any particular official name like "amserdam" or
> > "beijing" if this is your concern.
> >
> > Thanks
> > Jess
> >
> > On Tue Jan 02 03:04:23 2018, zhao.huab...@zte.com.cn wrote:
> > > Hi Jess,
> > >
> > >
> > > 1.1.0 is just a snapshot version right now, so it should not be
> > > released at this point. Do we have a workaround for this issue?
> > >
> > >
> > > Thanks,
> > >
> > >
> > > Huabing
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Original Mail
> > >
> > >
> > >
> > > Sender:  ;
> > > To: zhaohuabing10201488;
> > > CC:  ;
> > > Date: 2017/12/30 02:12
> > > Subject: [ONAP Helpdesk #50378] Jenkins jobs failed (due to
> > > snapshot
> > > repository setting?)
> > >
> > >
> > > Dear Huabing,
> > >
> > > This is the last released version we had for these binaries:
> > > https://nexus.onap.org/content/repositories/releases/org/onap/msb/apigateway/apiroute/apiroute-
> > > standalone/
> > >
> > > Looks like we need to make a release for version 1.1.0. Do you have
> > > a
> > > candidate for this version that we can release?
> > >
> > > Thanks!
> > >   Jess.
> > >
> > > On Tue Dec 26 04:17:29 2017, zhao.huab...@zte.com.cn wrote:
> > > > Dear ONAP helpdesk,
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > I noticed that some of the jenkins jobs are continually failing,
> > > > it
> > > > seems that the snapshot repository is missing in the ONAP maven
> > > > setting.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > One failed Jenkins job:
> > > > https://jenkins.onap.org/view/msb/job/msb-
> > > > apigateway-master-stage-site-java/
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-
> > > > site-
> > > > plugin:3.6:site (default-cli) on project msb-apigateway-parent:
> > > > failed
> > > > to get report for org.apache.maven.plugins:maven-javadoc-plugin:
> > > > Failed to execute goal on project apiroute-standalone: Could not
> > > > resolve dependencies for project
> > > > org.onap.msb.apigateway.apiroute:apiroute-standalone:pom:1.1.0:
> > > > Could
> > > > not find artifact 

[onap-discuss] Jenkins jobs failed (due to snapshot repository setting?)

[zhao.huabing]

Dear ONAP helpdesk,






I noticed that some of the jenkins jobs are continually failing, it seems that 
the snapshot repository is missing in the ONAP maven setting.






One failed Jenkins job: 
https://jenkins.onap.org/view/msb/job/msb-apigateway-master-stage-site-java/ 





[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.6:site (default-cli) on project 
msb-apigateway-parent: failed to get report for 
org.apache.maven.plugins:maven-javadoc-plugin: Failed to execute goal on 
project apiroute-standalone: Could not resolve dependencies for project 
org.onap.msb.apigateway.apiroute:apiroute-standalone:pom:1.1.0: Could not find 
artifact org.onap.msb.apigateway.apiroute:apiroute-service:jar:1.1.0 in 
releases (https://nexus.onap.org/content/repositories/releases/) -> [Help 
1]13:15:21 [ERROR] 




Thanks,


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

[onap-discuss] Reply: [modeling] ONAP Modeling Workshop on Thursday

[zhao.huabing]

Hi,

Can I download the presented slide deck at somewhere?

Thanks,
Huabing




Original Message



From:denghui(L);
To:onap-discuss@lists.onap.org;
Date:2017-12-14 09:51:49
Subject:[onap-discuss] [modeling] ONAP Modeling Workshop on Thursday


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

 


 
Hello all

 
 

 
Tomorrow workshop venue address is:

 Huawei Technologies

 Checkin: Bldg B

 Meeting Venue: Bldg C 1F-05 Training Room

 2330 Central Expressway

 Santa Clara,  CA 95050

 
 

 
Check-in Instruction:

 
1) All attendees must use self sign in system to check in at the main reception 
desk located at Bldg B lobby.

 
For any external guests who bring in their own laptops must sign a laptop 
registration form at the sign in, name tag will be issued afterwards.  

 
 

 
2) Follow the conference sign to the meeting room in Bldg C.

 
 

 
Time

 
Topic

 
Prime

 
09:00 - 09:05

 
Host welcome and facility

 
Huawei

 
09:05 - 09:10

 
 ONAP President

 
Yacheng Wang

 
09:10 - 10:50

 
SDO Session

 
09:10 - 09:30

 
MEF

 
John

 
09:30 - 09:50

 
TMF

 
John Wilmes

 
09:50 - 10:10

 
 ONF

 
Nigel

 
10:10 - 10:30

 
ETSI NFVETSI NFV

 
Andrei and Shitao

 
10:30 - 10:50

 
OASIS TOSCA

 
Shitao & Alex

 
10:50 - 11:00

 
Break

 
11:00 - 12:00

 
CIM discussion

 
Lingli/Andy/John

 
12:00 - 13:00

 
Lunch

 
13:00 - 14:00

 
Resource Session

 
Andy & David & Yangxu

 
13:00 - 13:30

 
Resource IM

 
13:00 - 14:00

 
Resource DT DM

 
14:00 - 15:00

 
Service Session

 
Lingli & Maopeng & David

 
14:00 - 14:30

 
Service IM

 
14:30 - 15:00

 
Service DT DM

 
15:00 - 15:30

 
RT DM A

 
Jimmy & Yangxu & Maopeng

 
 15:30 - 16:00

 
Close Loop Automation Model 

 
 Ron Shacham

 
 16:00 - 16:30

 
MultiVIM FCAPS Model

 
 Xinhui Li

 
 16:30 - 17:00

 
Wrapup 

 
 

 
Looking forward to seeing you tomorrow

 
Best regards,

 
 

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

[onap-discuss] About Image Manager Project Proposal

[zhao.huabing]

Hi Gildas and all,






I have requested to defer the Image Manager Project proposal at this week's TSC 
meeting. But after that, we receive some feedback from the community that the 
requirements of Image Manager is important for operators.


So we'd like to add this project back to the F2F project proposal agenda to 
discuss with the TSC and figure out the way going forward.






Thanks,


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

[onap-discuss] Get errors when deploying AAI via OOM

[zhao.huabing]

Hi,






I got the below errors when deploying AAI via OOM.


./createAll.bash -a aai -n onap


kubectl get pods -n onap-aai






elasticsearch-622738319-71vjg   0/1   rpc error: code = 2 desc = 
failed to start container 
"698a9bc2989c227a34b91018fe0f840b2f293bcb9daceb50ec36c7550308374e": Error 
response from daemon: {"message":"invalid header field value \"oci runtime 
error: container_linux.go:247: starting container process caused 
\\\"process_linux.go:359: container init caused \\\"rootfs_linux.go:53: 
mounting 
\\\"/dockerdata-nfs/onap/aai/elasticsearch/config/elasticsearch.yml\\\"
 to rootfs 
\\\"/var/lib/docker/aufs/mnt/d24d0f3bbefe3274713a8b518ef22382af64e379f5dfff823197792d7a226821\\\"
 at 
\\\"/var/lib/docker/aufs/mnt/d24d0f3bbefe3274713a8b518ef22382af64e379f5dfff823197792d7a226821/usr/share/elasticsearch/config/elasticsearch.yml\\\"
 caused \\\"not a directory\\\"\\\"\\\"\\n\""}


 



sparky-be-1292339831-ncldx  0/2   rpc error: code = 2 desc = 
failed to start container 
"c6574fe2e3fd7544234e97b24aadd46a613be2be348c4273edd68962102cfa2c": Error 
response from daemon: {"message":"invalid header field value \"oci runtime 
error: container_linux.go:247: starting container process caused 
\\\"process_linux.go:359: container init caused \\\"rootfs_linux.go:53: 
mounting 
\\\"/dockerdata-nfs/onap/log/filebeat/log4j/filebeat.yml\\\"
 to rootfs 
\\\"/var/lib/docker/aufs/mnt/a9bbf536908afe8eab4aa9cfda6bd3bbb1e4b9d62ac1a1b2a50a7e4487f1b12a\\\"
 at 
\\\"/var/lib/docker/aufs/mnt/a9bbf536908afe8eab4aa9cfda6bd3bbb1e4b9d62ac1a1b2a50a7e4487f1b12a/usr/share/filebeat/filebeat.yml\\\"
 caused \\\"not a directory\\\"\\\"\\\"\\n\""}  






Any idea?







Thanks,


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

Re: [onap-discuss] [ptls] Please complete Beijing Software ArchitectureSurvey

[zhao.huabing]

Hi Jason,


Yes,I think this question makes more sense because the internal API Gateway 
will evolve towards a sidecar approach which we'd like to promote.


Thanks,


Huabing







Original Mail



Sender:  ;
To: zhaohuabing10201488;
CC:  ; ;
Date: 2017/11/30 03:22
Subject: Re:[onap-discuss] [ptls] Please complete Beijing Software 
ArchitectureSurvey 


Huabing,

Thanks for your input and for being the first to complete the survey!

If I understand your comments, *all* projects by default are using MSB through 
the service registration.  Would the question be more clear to ask if they are 
using the internal API Gateway?

By the way, the service mesh approach sounds great.


Regards,
Jason Hunt 
Executive Software Architect, IBM 

Phone: 314-749-7422
Email: djh...@us.ibm.com
Twitter: @DJHunt
 



From:
To:
Cc:, 
Date:11/29/2017 03:26 AM
Subject:Re:[onap-discuss] [ptls] Please complete Beijing Software 
ArchitectureSurvey 





Hi Jason,


Thank you for the great effort and it's really helpful to reach our Beijing 
release goal!




I just want to clarify the question " Do you use MSB?" in the Survey because it 
may be confusing for the ptls.




As I presented at this week's Arch call, one of the most important design 
principles of MSB is providing Microservice Infrastructure which is transparent 
to the applications. So the projects can leverage the capability of MSB with 
minimum cost. It’s crucial because ONAP projects are polyglot and using 
different lib/framework.




For registration:

In Amsterdam release, MSB integrated with both OOM and heat template to 
automatically register service endpoints for all the microservices of ONAP 
project. 




For service communication:

The Internal API Gateway can handle the inter-service communication details 
including service discovery and load balancing without modification on the 
application side.




For Beijing and going forward, MSB will be continually evolving to support 
Carrier Grade Microservice Architecture for ONAP with Service Mesh.




Thanks,

Huabing


Original Mail

Sender:  ;
To:  ;
CC:  ;
Date: 2017/11/28 06:51
Subject: [onap-discuss] [ptls] Please complete Beijing Software 
ArchitectureSurvey
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Hi PTLs, 

With the Beijing focus on platform maturity (S3P/Carrier Grade) and software 
architecture, the architecture subcommittee would like to gather some 
information from the projects about the technology used, maturity evaluation, & 
skills.  We have created a survey at: 

https://www.surveymonkey.com/r/X9F6HK6

Please complete this survey by next Wednesday Dec. 6th, so that we can 
consolidate the information for our Santa Clara meeting. 

If you have questions or would prefer to discuss in a call, please let me know. 
 Also, if some of the information requested is available in your documentation, 
please just provide a pointer in the survey. 

THANK YOU! 


Regards,
Jason Hunt 
Executive Software Architect, IBM 

Phone: 314-749-7422
Email: djh...@us.ibm.com 
Twitter: @DJHunt___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [msb] Cannot access Services through MSB

[zhao.huabing]

Hi Audhut,






If you're using K8s/OOM approach to deploy ONAP, all the services should be 
automatically registered to MSB by kube2msb registrator.


kube2msb registrator is watching the kubernetes events and get service 
endpoints information form the annotation of config and use that information to 
register the services to MSB. Detailed introduction can be found 
here:https://wiki.onap.org/display/DW/Microservices+Bus+Tutorial 






I guess the reason is that you didn't specify the kubernetes API token in the 
oom/kubernetes/kube2msb/values.yaml config file, kube2msb-registrator need it 
to access the kubernetes master. 


Please replace the token in red with the token in your kubernetes environment, 
you can find it in  ~/.kube/config



nsPrefix: onap

pullPolicy: IfNotPresent

image:

  kube2msb: nexus3.onap.org:10001/onap/oom/kube2msb

kubeMasterUrl: https://kubernetes.default.svc.cluster.local:443

discoveryUrl: http://msb-discovery.onap-msb:10081

kubeMasterAuthToken: 
QmFzaWMgTURrd056VXdSVEk1TVRGRk9UaEVOREJCTWprNlpHTnlaSGt4YzJsSVlsRlVZVU16WTFsUk1XWnZhV0UyY21GRWEwNUhkMDFDVWxORVRIUmlZUT09




MSB internal api gateway is exposed on nodeport 30080, once you get all the 
services running, you can browse all the registered services on the MSB portal  
http://{HOST_IP}:30080/msb .




BR,

Huabing







Original Mail



Sender:  ;
To: zhaohuabing10201488;
CC:  ;
Date: 2017/11/29 19:29
Subject: RE: Re:[onap-discuss] [msb] Cannot access Services through MSB




Hi  Zhao,


Tried it but without any luck.


I am executing this on the onap k8s env and I have observed that one of the POD 
is down - kube2msb-registrator-1900608333-06b2p. Could that be the reason? What 
 is the main function of this POD?


What are the other containers


-  msb-eag-565007981-vgnth – is this the external gateway


-  msb-iag-3532976410-8xf0c – is this the internal gateway


 


Is there a way to check if the service is registered in the internal gateway.


 


I will check once I get the registrator pod running.


 


Thanks,


Avdhut Kholkar


From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn] 
 Sent: Wednesday, November 29, 2017 1:33 PM
 To: Avdhut Kholkar 
 Cc: onap-discuss@lists.onap.org
 Subject: Re:[onap-discuss] [msb] Cannot access Services through MSB


 

Hi Avdhut,

 

It seems like the AAI service has not been successfully registered to MSB.

 

Could you please try this curl command and send me the output?

 

curl -X POST \
 -H "Content-Type: application/json" \
 -d '{"serviceName": "aai", "version": "v8", "url": "/aai/v8","protocol": 
"REST", "path": "/aai/v8", "nodes": [ {"ip": "{AAI_IP}","port": "8443"}]}' \
 "http://127.0.0.1:10081/api/microservices/v1/services;

 

Thanks,

Huabing

 

Original Mail



Sender:  ;



To:  ;



Date: 2017/11/29 14:36



Subject: [onap-discuss] [msb] Cannot access Services through MSB




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


Hi,


 


I have followed instructions mentioned over page: 
https://wiki.onap.org/display/DW/MSB+Test+Environment+Setup 


I have registered AAI service in MSB as mentioned in the wiki above


{


  "serviceName": "aai",


  "version": "v8",


  "url": "/aai/v11",


  "protocol": "REST",


  "visualRange": "1",


  "path":"/aai/v11",


  "nodes": [


{


  "ip": "10.235.34.13",


  "port": "40325",


  "ttl": 0


}


  ]


}


 


If I access the URL directly from AAI it works


https://:/aai/v8/cloud-infrastructure/cloud-regions


Response: 200 OK


{


"cloud-region": [


{


"cloud-owner": "OnapPrivateCloud",


"cloud-region-id": "RegionOne",


"cloud-type": "SharedNode",


"owner-defined-type": "OwnerType",


"cloud-region-version": "v1",


"cloud-zone": "CloudZone",


"resource-version": "1511873022465",


"tenants": {


"tenant": [


{


"tenant-id": "{{tenant_id}}",


"tenant-name": "onap-dev",


"resource-version": "1511873022533"


}


]


}


}


]


}


 


But If I access through MSB API, I get a ‘BAD Gateway’ error


 


GET 
/api/aai/v8/cloud-infrastructure/cloud-regions/cloud-region/OnapPrivateCloud/RegionOne


Host: 10.235.34.13: 40325


Content-Type: application/json


X-FromAppId: AAI


Accept: application/json


 


Response: 502 Bad Gateway








502 Bad Gateway











502 Bad Gateway





error message:No route found for this request!





nginx








 


I also tried by 

Re: [onap-discuss] [ptls] Please complete Beijing Software ArchitectureSurvey

[zhao.huabing]

Hi Jason,






Thank you for the great effort and it's really helpful to reach our Beijing 
release goal!






I just want to clarify the question " Do you use MSB?" in the Survey because it 
may be confusing for the ptls.







As I presented at this week's Arch call, one of the most important design 
principles of MSB is providing Microservice Infrastructure which is transparent 
to the applications. So the projects can leverage the capability of MSB with 
minimum cost. It’s crucial because ONAP projects are polyglot and using 
different lib/framework.






For registration:


In Amsterdam release, MSB integrated with both OOM and heat template to 
automatically register service endpoints for all the microservices of ONAP 
project. 






For service communication:


The Internal API Gateway can handle the inter-service communication details 
including service discovery and load balancing without modification on the 
application side.






For Beijing and going forward, MSB will be continually evolving to support 
Carrier Grade Microservice Architecture for ONAP with Service Mesh.






Thanks,


Huabing



Original Mail



Sender:  ;
To:  ;
CC:  ;
Date: 2017/11/28 06:51
Subject: [onap-discuss] [ptls] Please complete Beijing Software 
ArchitectureSurvey


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

Hi PTLs, 
 
With the Beijing focus on platform maturity (S3P/Carrier Grade) and software 
architecture, the architecture subcommittee would like to gather some 
information from the projects about the technology used, maturity evaluation, & 
skills.  We have created a survey at: 
 
https://www.surveymonkey.com/r/X9F6HK6 
 
Please complete this survey by next Wednesday Dec. 6th, so that we can 
consolidate the information for our Santa Clara meeting. 
 
If you have questions or would prefer to discuss in a call, please let me know. 
 Also, if some of the information requested is available in your documentation, 
please just provide a pointer in the survey. 
 
THANK YOU! 
 

Regards,
Jason Hunt 
Executive Software Architect, IBM 
 
Phone: 314-749-7422
Email: djh...@us.ibm.com 
Twitter: @DJHunt___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [msb] Cannot access Services through MSB

[zhao.huabing]

Hi Avdhut,






It seems like the AAI service has not been successfully registered to MSB.






Could you please try this curl command and send me the output?






curl -X POST \-H "Content-Type: application/json" \-d '{"serviceName": "aai", 
"version": "v8", "url": "/aai/v8","protocol": "REST", "path": "/aai/v8", 
"nodes": [ {"ip": "{AAI_IP}","port": "8443"}]}' 
\"http://127.0.0.1:10081/api/microservices/v1/services;






Thanks,


Huabing






Original Mail





Sender:  ;
To:  ;
Date: 2017/11/29 14:36
Subject: [onap-discuss] [msb] Cannot access Services through MSB


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

 

Hi,


 


I have followed instructions mentioned over page: 
https://wiki.onap.org/display/DW/MSB+Test+Environment+Setup 


I have registered AAI service in MSB as mentioned in the wiki above


{


  "serviceName": "aai",


  "version": "v8",


  "url": "/aai/v11",


  "protocol": "REST",


  "visualRange": "1",


  "path":"/aai/v11",


  "nodes": [


{


  "ip": "10.235.34.13",


  "port": "40325",


  "ttl": 0


}


  ]


}


 


If I access the URL directly from AAI it works


https://:/aai/v8/cloud-infrastructure/cloud-regions


Response: 200 OK


{


"cloud-region": [


{


"cloud-owner": "OnapPrivateCloud",


"cloud-region-id": "RegionOne",


"cloud-type": "SharedNode",


"owner-defined-type": "OwnerType",


"cloud-region-version": "v1",


"cloud-zone": "CloudZone",


"resource-version": "1511873022465",


"tenants": {


"tenant": [


{


"tenant-id": "{{tenant_id}}",


"tenant-name": "onap-dev",


"resource-version": "1511873022533"


}


]


}


}


]


}


 


But If I access through MSB API, I get a ‘BAD Gateway’ error


 


GET 
/api/aai/v8/cloud-infrastructure/cloud-regions/cloud-region/OnapPrivateCloud/RegionOne


Host: 10.235.34.13: 40325


Content-Type: application/json


X-FromAppId: AAI


Accept: application/json


 


Response: 502 Bad Gateway








502 Bad Gateway











502 Bad Gateway





error message:No route found for this request!





nginx








 


I also tried by registering a SO URL and have the same issue. I am able to 
access the SO URL directly but via MSB.


Note that my env did not register the services directly via ESR – this should 
not make a difference I think.


 


Can someone help?





Regards,


Avdhut



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


Amdocs Development Centre India Private Limited having CIN: 
U72200PN2004PTC0188320 converted into Amdocs Development Centre India LLP (A 
limited liability partner­ship with LLP Identification Number: AAI-6901 
effective 28th Feb 2017)___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] MSB to support Microservice Infrastructure for Carrier Grade ONAP - Service Mesh and others

[zhao.huabing]

Hi Chris,




May I request to add a topic to this week's call to discuss this "MSB  to 
support Microservice Infrastructure for Carrier Grade ONAP - Service Mesh and 
others"?




Abstract:

In Amsterdam Release, MSB provides infrastructure to support ONA Microservices 
architecture including service registration/discovery, API gateway and JAVA 
SDK. To evolve towards a carrier-grade platform, ONAP Microservices need to 
improve its reliability and security of inter-services communication, 
visibility of microservices metrics, manageability of microservices such as 
policy, API management, Configure management and performance, etc. MSB is to 
introduce Service Mesh, the next-generation Microservices to address these 
challenges.







Thanks,

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

Re: [onap-discuss] query About MSB and MSB_IP_Address

[zhao.huabing]

Got it.


Thanks for the correction.











Original Mail



Sender:  ;
To: zhaohuabing10201488; ;
CC:  ;
Date: 2017/11/24 10:31
Subject: RE: [onap-discuss] query About MSB and MSB_IP_Address




Hi Huabing,


 


   The latest heat template rename the OPEN-O vm to multi-service .


 


Best Regards,


Bin Yang,Solution Readiness Team,Wind River


Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189


Skype: yangbincs993


 


From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn] 
 Sent: Friday, November 24, 2017 10:25 AM
 To: Yang, Bin; guptagau...@vmware.com
 Cc: onap-discuss@lists.onap.org
 Subject: Re: [onap-discuss] query About MSB and MSB_IP_Address


 

Hi Yang, Gaurav,

 

I think MSB is hosted in the OPEN-O VM.

Take a look at these two scripts in the demo gerrit reop:

demo\heat\ONAP\onap_openstack.yaml line 1576 

./openo_install.sh

 

demo\boot\openo_install.sh line line 58

curl -k $NEXUS_REPO/org.onap.demo/boot/$ARTIFACTS_VERSION/msb_vm_init.sh -o 
/opt/msb_vm_init.sh

 

demo\boot\openo_all_serv.sh line 3

bash /opt/msb_vm_init.sh &>/dev/null 

 

MSB docker is spup up in this script: demo\boot\msb_vm_init.sh

 

BR,

Huabing


Original Mail



Sender:  ;



To:  ; ;



Date: 2017/11/24 09:33



Subject: Re: [onap-discuss] query About MSB and MSB_IP_Address




Hi Gaurav,


 


   The MSB services run over VM named as 
{onap_vm_prefix}-multi-service as micro-services.


 


Best Regards,


Bin Yang,Solution Readiness Team,Wind River


Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189


Skype: yangbincs993



 



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gaurav Gupta (c)
 Sent: Thursday, November 23, 2017 10:31 PM
 To: onap-discuss@lists.onap.org
 Subject: [onap-discuss] query About MSB and MSB_IP_Address




 


Hi All 

 

While running the vFW Demo - We are trying to look for which VM is hosting MSB  
.

 

As per the robot HealthCheck also we donot see MSB  .

We also donot see any mention of MSB Host VM or container inside ONAP heat 
environment file . 

 

can some one pls help us with this information . 

 

thanks in advance for the same 

 

 

with best regards

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

Re: [onap-discuss] Request to consider reschedule the weekly callsfor DST time changes

[zhao.huabing]

Hi Mazin, Lingli and all,






May I suggest applying this principle to all the community meetings? I noticed 
that there are a couple of other meetings that have the same problem.






Thanks,


Huabing











Original Mail



Sender:  ;
To:  ;
CC:  ;
Date: 2017/11/21 10:38
Subject: Re: [onap-discuss] Request to consider reschedule the weekly callsfor 
DST time changes


I am very supportive. We agreed to avoid 12 mid night to 6am. 
 
Kenny, please advise of when we can make the change. TSC meetings

should go back to 1 hour.

 

Mazin 



 


 
 
On Nov 20, 2017, at 8:45 PM, Lingli Deng  wrote:
 


Hi Kenny and Mazin,

 

As a result of the DST time change, the current time slot for ONAP calls are 
technically one-hour later for regions that does not follow the practice in 
winter, like China. 

Hence a lot of them, including TSC weekly call, are now spanning after 
mid-night.

As we requested last week on the TSC call, would it be possible to reschedule 
the weekly calls 30 minutes earlier, so that people could share the burden of 
accommodating the change?

 

Thanks,

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

Re: [onap-discuss] [E] Centralized Image Management proposaldiscussion

[zhao.huabing]

Hi Viswa,






It's the same proposal I presented at the SDC weekly meeting, but with some 
modification to reflect the collected feedback.






We got a suggestion that Image Management covers both the design time and run 
time and it should better be discussed more broadly in the community. That's 
why Lizi reached to Arch subcommittee.






Thanks,


Huabing



Original Mail



Sender:  ;
To: lizi00164331;
CC:  ; ;
Date: 2017/11/15 20:55
Subject: Re: [onap-discuss] [E] Centralized Image Management proposaldiscussion



Dear All,
I have a question as to whether this proposal ( Centralized Image management ) 
conflicts with SDC Image management proposal, that was proposed earlier ?

BR,
Viswa








Viswanath Kumar Skand Priya
Architect
Verizon Network Ops & Eng







On Wed, Nov 15, 2017 at 2:10 PM,   wrote:






Hi Chris and all,






As discussed in last Architecture meeting, I have update the Image manage 
powerpoint. Please see the attachment. If you have any question or suggestion, 
please don't hesitate to tell me.






To Chris: If do the image validation check with VNF-SDK. What the sequnce would 
be like? What the output data would be after the VNF-SDK checked the images?



















___
 onap-discuss mailing list
 onap-discuss@lists.onap.org
 
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ=9F3pNUkzjE-2v1eTClkRVakDRN8GH7Bm-wt1lWkxoUyyDORTqf5MxNO_GrMBs0gZ=5TpzLl1CEJmxeMuHEcfkD8FyhB3E4HTFKvWpDIe7wjs=642o4rh5qd0sNTjtC8lxlRurnblMRn1TRrFzXl26Ln4=___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] No binaries in ONAP stagging repo

[zhao.huabing]

Hi Jess, Gary,


I found that the binary of msb java sdk has not been pushed to ONAP stagging 
repository today.


Because of that, the wfengine jenkins job failed.


https://jenkins.onap.org/view/vfc/job/vfc-nfvo-wfengine-master-engine-activiti-extension-verify-java/
 






The msb-java-sdk-1.0.0 does exist at https://nexus.onap.org in repository 
autorelease-18453 (staging: closed), but not in stagging repo.






Is there anything I am supposed to do to fix this?






Thanks a lot,


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

Re: [onap-discuss] 答复: RE: sdc integrate workflow designer

[zhao.huabing]

Hi Michael,


Does it mean that if Workflow Designer needs to talk with its backend, it has 
to add some proxy logic to the FeProxyServlet? 


We might need to reconsider this approach because it adds coupling between the 
SDC server and the integrated designers.  Given that a number of designers such 
as workflow designer, control loop designer, control loop configurator, policy 
designer are planning to move into SDC,the FeProxyServlet may become too big to 
maintain. I suggest we can use MSB API gateway as a reverse proxy to solve this 
issue.





Thanks,


Huabing











Original Mail



Sender:  ;
To: zhaohuabing10201488; ;
CC: yuanhu10090474;fujinhua10108953; ;
Date: 2017/10/16 15:48
Subject: RE: [onap-discuss]答复: RE: sdc integrate workflow designer








Hi,


Since we will not be using the work flow as part of the use case in R1.


I do not want to direct resource from the work on R1.


 


We need to do this work as part of R2 with a real integration.


 


In addition we need to provide a guide line for designers joining SDC,


 


Because we need a specific ui configuration and sdc serves as a proxy for 
communication between the UI and BE components of different designers.


 


 


 


 


 


BR,


 


Michael Lando


Opensource TL , SDC


AT Network Application Development · NetCom  


Tel Aviv | Tampa | Atlanta | New Jersey |Chicago


···


Office: +972 (3) 5451487


Mobile: +972 (54) 7833603


e-mail: ml6...@intl.att.com


 


From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn] 
 Sent: Monday, October 16, 2017 9:50 AM
 To: SHADMI, DAVID ; Lando,Michael 
 Cc: yuan@zte.com.cn; fu.jin...@zte.com.cn; onap-discuss@lists.onap.org
 Subject: Re: [onap-discuss]答复: RE: sdc integrate workflow designer


 

Hi David, Michael,

 

I talked with Lv bo, It turns out that he has no idea how to add the workflow 
button to SDC menubar.  Can someone in SDC team help with this?

 

Thanks a lot,

Huabing

 


Original Mail



Sender:  ;



To: YuanHu10090474; ;



CC: FuJinHua10108953; ;



Date: 2017/10/13 21:53



Subject: Re: [onap-discuss]答复:  RE: sdc integrate workflow designer




 



I believe the question is to Lv Bo as he has this task.


 


Thanks,


David


 


From: yuan@zte.com.cn [mailto:yuan@zte.com.cn] 
 Sent: Friday, October 13, 2017 1:09 AM
 To: LANDO, MICHAEL ; SHADMI, DAVID 
 Cc: LANDO, MICHAEL ; onap-discuss@lists.onap.org; 
lv.bo...@zte.com.cn; fu.jin...@zte.com.cn
 Subject: 答复: [onap-discuss] 答复: RE: sdc integrate workflow designer


 

Hi Michael and David,

 

Does the latest version of SDC have been integrated with the Workflow Designer?

 

Thanks,

Yuan Hu

 

 


原始邮件



发件人：吕波10185543



收件人： ;



抄送人： ;



日 期 ：2017年09月28日 13:56



主 题 ：[onap-discuss] 答复: RE: sdc integrate workflow designer




 


How about the result?

 

 




发件人： ;



收件人：吕波10185543;



抄送人： ;



日 期 ：2017年09月25日 17:40



主 题 ：RE: sdc integrate workflow designer




 


I will check this.


 


 


 


 


 


 


 


BR,


 


Michael Lando


Opensource TL , SDC


AT Network Application Development · NetCom  


Tel Aviv | Tampa | Atlanta | New Jersey |Chicago


···


Office: +972 (3) 5451487


Mobile: +972 (54) 7833603


e-mail: ml6...@intl.att.com


 


From: lv.bo...@zte.com.cn [mailto:lv.bo...@zte.com.cn] 
 Sent: Monday, September 25, 2017 5:37 AM
 To: Lando,Michael 
 Cc: onap-discuss@lists.onap.org
 Subject: sdc integrate workflow designer


 

 

Hi Michael, 

 

As we disccussed before, workflow designer will be integrated into sdc as a 
button in top menu(see the image below). 



 

This jira task is assigned to me. And I found this code is under 
sdc/catalog-ui. could I just add a button to the top menu after 'CATALOG' or I 
need to notice the one who is response for thiscomponent to integrate the 
workflow designer?  

 

Regards.

 

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

Re: [onap-discuss] 答复: RE: sdc integrate workflow designer

[zhao.huabing]

Hi David, Michael,






I talked with Lv bo, It turns out that he has no idea how to add the workflow 
button to SDC menubar.  Can someone in SDC team help with this?






Thanks a lot,


Huabing











Original Mail



Sender:  ;
To: YuanHu10090474; ;
CC: FuJinHua10108953; ;
Date: 2017/10/13 21:53
Subject: Re: [onap-discuss]答复: RE: sdc integrate workflow designer








I believe the question is to Lv Bo as he has this task.


 


Thanks,


David


 


From: yuan@zte.com.cn [mailto:yuan@zte.com.cn] 
 Sent: Friday, October 13, 2017 1:09 AM
 To: LANDO, MICHAEL ; SHADMI, DAVID 
 Cc: LANDO, MICHAEL ; onap-discuss@lists.onap.org; 
lv.bo...@zte.com.cn; fu.jin...@zte.com.cn
 Subject: 答复: [onap-discuss] 答复: RE: sdc integrate workflow designer


 

Hi Michael and David,

 

Does the latest version of SDC have been integrated with the Workflow Designer?

 

Thanks,

Yuan Hu

 

 


原始邮件



发件人：吕波10185543



收件人： ;



抄送人： ;



日 期 ：2017年09月28日 13:56



主 题 ：[onap-discuss] 答复: RE: sdc integrate workflow designer




 


How about the result?

 

 




发件人： ;



收件人：吕波10185543;



抄送人： ;



日 期 ：2017年09月25日 17:40



主 题 ：RE: sdc integrate workflow designer




 


I will check this.


 


 


 


 


 


 


 


BR,


 


Michael Lando


Opensource TL , SDC


AT Network Application Development · NetCom  


Tel Aviv | Tampa | Atlanta | New Jersey |Chicago


···


Office: +972 (3) 5451487


Mobile: +972 (54) 7833603


e-mail: ml6...@intl.att.com


 


From: lv.bo...@zte.com.cn [mailto:lv.bo...@zte.com.cn] 
 Sent: Monday, September 25, 2017 5:37 AM
 To: Lando,Michael 
 Cc: onap-discuss@lists.onap.org
 Subject: sdc integrate workflow designer


 

 

Hi Michael, 

 

As we disccussed before, workflow designer will be integrated into sdc as a 
button in top menu(see the image below). 



 

This jira task is assigned to me. And I found this code is under 
sdc/catalog-ui. could I just add a button to the top menu after 'CATALOG' or I 
need to notice the one who is response for this   component to integrate the 
workflow designer?  

 

Regards.

 

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

Re: [onap-discuss] VNF package import and onboarding

[zhao.huabing]

Hi Tal,


Could we use Zoom instead?  Connect online meeting is not stable in China, we 
had difficult using it last time.






We can use ZTE's zoom Bridge https://zoom.us/j/66 if it's too late to 
ask LF to provide the Zoom Bridge.






Thanks,


Huabing



Original Mail



Sender:  ;
To:  ; ; 
;zhaohuabing10201488;lizi00164331;FengYuanXing10034308;YuanHu10090474;
 ;
Date: 2017/10/10 16:21
Subject: VNF package import and onboarding










VNF package import and onboarding





Dear zhaohuabing10201488：






Hello! You are invited to join the meeting organized by  .







Subject：




VNF package import and 
onboarding








Time：





2017-10-10 17:30 ~ 18:00 (Beijing Time UTC +8:00)








Venue：




(AT Connect online 
meeting at https://connect10.uc.att.com/alphatest/meet/?ExEventID=89855626=M 
- Details below)








Information：




VNF package import and 
onboarding








Participant：






tg8...@intl.att.com,

tg8...@intl.att.com,

ds2...@att.com,

onap-discuss@lists.onap.org,

zhaohuabing10201488,

lizi00164331,

FengYuanXing10034308,

YuanHu10090474,

ml6...@intl.att.com,





   To join AT Connect Conference:

Click here: https://connect10.uc.att.com/alphatest/meet/?ExEventID=89855626=M
 For dialing-in only:
---
1.Dial one of the numbers listed below
2. When prompted, enter the meeting access code: 9855626#
  * Toll-Free Number (in ISRAEL): 1-809-413-184.
  * Blackberry (Toll-Free Number): 1809413184x9855626#
  * iPhone / Android (Toll-Free Number): 1809413184,,9855626#
  * Windows Phone (Toll-Free Number): tel:1809413184,,9855626#,
On-site number(s):
* test: 
  * A number in your country or in a country close to you (may be toll 
free): 
https://www.teleconference.att.com/servlet/glbAccess?process=1=1809413184=0
   Powered by AT Connect.
   



Notice is hereby notified!






Organizer：  

Mail time：2017-10-10 
17:30 ~ 18:00 (Beijing Time UTC +8:00)___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Reply:[Onap-release] Agenda for M4 Code Review on Sept 28

[zhao.huabing]

Hi Gildas,

Attached please find the evidence for MSB discovery UT coverage.

There's no unit test for swagger SDK yet, I'd like to exclude the swagger SDK 
binary from MSB Amsterdam release because It's not a must-have feature for 
Amsterdam.

Please let me know if there's any other issues which are preventing MSB from 
passing M4.

Thanks,
Huabing



Original Message



From:GildasLanilis;
To:onap-rele...@lists.onap.org;
Cc:GILBERT, MAZIN E (MAZIN E);Phil Robb;onap-discuss@lists.onap.org;
Date:2017-09-28 04:58:27
Subject:[Onap-release] Agenda for M4 Code Review on Sept 28


 


 
Hi PTLs,

 
 

 
This message is regarding the M4 Code Freeze for Sept 28.

 
We had to breakdown the M4 review in 2 meetings: 1 meeting from 10 am to 12 pm 
(for people in China, and those who need to take-off in the afternoon) and a 
second from 1 pm to 3 pm (for people in the US and those who have extra time in 
the afternoon).

 
Time is Paris time zone.

 
 

 
If you cannot make it, please send your delegate.

 
 

 
The agenda is available in wiki at 
https://wiki.onap.org/display/DW/Agenda+for+M4+Review 

 
 

 
Let me know if you have any question.

 
 

 
Thanks,

 
Gildas

 
 

 


 
Gildas Lanilis

 
ONAP Release Manager

 
Santa Clara CA, USA

 
gildas.lani...@huawei.com

 
Mobile: 1 415 238 6287___
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 Kanagaraj,




What we are discussing is part of the deployment of ONAP system, using shell 
and curl is much simpler than depending on an ONAP component to do that.




It introduces a "chicken or egg" question if we choose CLI to do that. :-)




Thanks,

Huabing






Original Mail



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







Dear Huabing and Marco,


 


I think we could use the CLI for registering services in to MSB. CLI is already 
having commands for it called “microservice-create”


So shall we make use of it. ?


 


Regards


Kanagaraj M


 


***
 
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**
 
 
***
 This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
 
***


 



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhao.huab...@zte.com.cn
 Sent: Thursday, September 21, 2017 11:55 AM
 To: plata...@research.att.com
 Cc: onap-discuss@lists.onap.org
 Subject: Re: [onap-discuss] Service registration with MSB //Re: [integration] 
ONAP installation via Heat 



 

Hi Marco,

 

I plan to use a shell script to register the services to MSB, the content of 
this script will looks like:

 

curl -X POST \

  -H "Content-Type: application/json" \

  -d '{"serviceName": "so", "version": "v1", "url": 
"/ecomp/mso/infra","protocol": "REST",  "nodes": [ {"ip": 
"${SO_IP_ADDRES}","port":  "8080"}]}' \

  "http://127.0.0.1:10081/api/microservices/v1/services”

 

This shell script can be called by msb_vm_init. These variables don't have to 
be passed to container.

 

Thanks,

Huabing 


Original Mail



Sender:  



To: zhaohuabing10201488



CC:    



Date: 2017/09/21 09:32



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




 



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

 

 





 



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: 

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

[zhao.huabing]

Hi Marco,




I plan to use a shell script to register the services to MSB, the content of 
this script will looks like:




curl -X POST \

  -H "Content-Type: application/json" \

  -d '{"serviceName": "so", "version": "v1", "url": 
"/ecomp/mso/infra","protocol": "REST",  "nodes": [ {"ip": 
"${SO_IP_ADDRES}","port": "8080"}]}' \

  "http://127.0.0.1:10081/api/microservices/v1/services”




This shell script can be called by msb_vm_init. These variables don't have to 
be passed to container.




Thanks,

Huabing 



Original Mail



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






 
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


 


 











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] 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] [onap-tsc] [integration][oom]How to use OOM to deploy ONAP atDeveloper Lab

[zhao.huabing]

Hi Mike,




MSB and kube2msb registrator have been added to the OOM oneclick script, 
https://gerrit.onap.org/r/#/c/12631/


Now if we use oneclick script to deploy ONAP, MSB will be deployed first and 
kube2msb registrator can registered all the service endpoints to MSB. 




Thanks,

Huabing







Original Mail



Sender:  
To:   
Date: 2017/09/14 22:51
Subject: [onap-tsc] [integration][oom]How to use OOM to deploy ONAP atDeveloper 
Lab





 When: Friday, September 15, 2017 7:00 AM-8:00 AM. (UTC-08:00) Pacific Time (US 
& Canada)
  Where: https://zoom.us/j/44
  
  *~*~*~*~*~*~*~*~*~*
  
In this session, Mike Elliott will give a demo and tutorial on how to use OOM 
to deploy ONAP at developer lab. It will be very helpful for people who are 
using developer lab to deploy ONAP and do integration testing.
  

  Regards,
  
Helen Chen
  

  Join from PC, Mac, Linux, iOS or Android: https://zoom..us/j/44
  Or iPhone one-tap (US Toll): +16465588656,44# or 
+14086380968,44#
  Or Telephone:
  Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
  Meeting ID: 44  8
  International numbers available: 
https://zoom.us/zoomconference?m=CqsAwHx4CSyRanCfPHKBvf6Vslgcsn86
  



[integration][oom]How to use OOM to deploy ONAP at Developer Lab




主题：




[integration][oom]How to use OOM to deploy ONAP at Developer Lab






时间：




2017-09-15 22:00:00(UTC+08:00) ~ 2017-09-15 23:00:00(UTC+08:00)






地点：




https://zoom.us/j/44






与会人：



onap-discuss@lists.onap.org,onap-...@lists.onap.org,




说明：




When: Friday, September 15, 2017 7:00 AM-8:00 AM. (UTC-08:00) Pacific Time (US 
& Canada)
Where: https://zoom.us/j/44

*~*~*~*~*~*~*~*~*~*

In this session, Mike Elliott will give a demo and tutorial on how to use OOM 
to deploy ONAP at developer lab. It will be very helpful for people who are 
using developer lab to deploy ONAP and do integration testing.



Regards,

Helen Chen



Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/44
Or iPhone one-tap (US Toll): +16465588656,44# or 
+14086380968,44#
Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
Meeting ID: 44  8
International numbers available: 
https://zoom.us/zoomconference?m=CqsAwHx4CSyRanCfPHKBvf6Vslgcsn86








特此通知！




组织者：helen.c...@huawei.com


创建时间：2017-09-14 22:47:12(UTC+08:00)






[integration][oom]How to use OOM to deploy ONAP at Developer Lab




SUMMARY:




[integration][oom]How to use OOM to deploy ONAP at Developer Lab






TIME:




2017-09-15 22:00:00(UTC+08:00) ~ 2017-09-15 23:00:00(UTC+08:00)






LOCATION:




https://zoom.us/j/44






ATTENDEES:



onap-discuss@lists.onap.org,onap-...@lists.onap.org,




DESCRIPTION:




When: Friday, September 15, 2017 7:00 AM-8:00 AM. (UTC-08:00) Pacific Time (US 
& Canada)
Where: https://zoom.us/j/44

*~*~*~*~*~*~*~*~*~*

In this session, Mike Elliott will give a demo and tutorial on how to use OOM 
to deploy ONAP at developer lab. It will be very helpful for people who are 
using developer lab to deploy ONAP and do integration testing.



Regards,

Helen Chen



Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/44
Or iPhone one-tap (US Toll): +16465588656,44# or 
+14086380968,44#
Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
Meeting ID: 44  8
International numbers available: 
https://zoom.us/zoomconference?m=CqsAwHx4CSyRanCfPHKBvf6Vslgcsn86








Notice is hereby notified!




ORGANIZER:helen.c...@huawei.com


CREATEDTIME:2017-09-14 22:47:12(UTC+08:00)___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] YOUR ACTION IS REQUIRED: Sonar naming convention

[zhao.huabing]

Thanks Jess and Gildas,

MSB is done.




Huabing








Original Mail



Sender:  
To:  
CC:   
Date: 2017/09/12 08:20
Subject: Re: [onap-discuss] YOUR ACTION IS REQUIRED: Sonar naming convention






Thank you everybody! :)

Also, small reminder please let's avoid removing projects from Sonar 


Thanks a ton
Jess




On Mon, Sep 11, 2017 at 4:49 PM, Gildas Lanilis  
wrote:



There are still 27 commits pending on this!!! You do not want to be the last 
one. Isn’t it J


Click that link now: 
https://gerrit.onap.org/r/#/q/status:open+topic:sonar-name-cleanup 


Please review and provide your disposition.

 
 


Thanks,


Gildas


ONAP Release Manager


1 415 238 6287



 



From: Gildas Lanilis 
 Sent: Friday, September 08, 2017 3:57 PM
 To: onap-discuss@lists.onap.org onap-rele...@lists.onap.org
 Cc: Jessica Wagantall' 
 Subject: YOUR ACTION IS REQUIRED: Sonar naming convention
 Importance: High



 
 


Thanks Jess for your contributions.


 


To All ONAP Code Reviewers, Committers and PTLs,


 


LF has been helping us in housekeeping Sonar. Currently, all names are upsides 
down. Once your action is performed, we should be able to quickly find relevant 
data info.


 


Please review the changes at 
https://gerrit.onap.org/r/#/q/status:open+topic:sonar-name-cleanup , provide 
your -1, +1,0,-2, +2 and merge the changes.


 


As Jess says below, once this is done, LF will help removing old entries.


 


Let’s see how fast we can get this done J…and then forget about it.


 


Thanks,


Gildas


ONAP Release Manager


1 415 238 6287


 


 


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


 


Dear Gildas, 


 


As discussed, for step #1 I have pushed into gerrit all corrections needed to 
all projects for their root pom files. The "" parameter has been set to 
match the name in gerrit (separated by dashes). 


 


These are the changes: 
https://gerrit.onap.org/r/#/q/status:open+topic:sonar-name-cleanup


 


Would you please help me communicating to the teams about the importance of 
getting these changes approved and merged? I now depend on them accepting my 
changes and any "-1" situations we can address them as it comes. 


 


These changes will generate new entries in Sonar, after that we can work on 
removing old entries. 


 


Thanks a ton in advance for your help!


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

Re: [onap-discuss] [OOM][MSB][Integration] OOM MSB Integrationfinished

[zhao.huabing]

Hi  Geora,




Thanks for raising this issue, I will be fixing it.




BR,

Huabing




















Original Mail



Sender:  
To:  zhaohuabing10201488 
CC:  
Date: 2017/09/09 05:33
Subject: RE: [onap-discuss] [OOM][MSB][Integration] OOM MSB Integrationfinished 







Hello,


 


I pulled the latest oom/msb from gerrit, but it was failing during the 
deployment into k8s due to missing docker repo  secret attribute in all msb  
deployment.yaml(s)


 


  imagePullSecrets:


  - name: "{{ .Values.nsPrefix }}-docker-registry-key"


 


 


I added it in my local environment and it solved the issue of


 


Failed to pull image "nexus3.onap.org:10001/onap/msb/msb_discovery:latest": rpc 
error: code = 2 desc = unauthorized: authentication  required


 


Thanks


Geora Barsky


647-946-5290


 





 


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


 



 



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arul Nambi
 Sent: Friday, September 8, 2017 4:03 PM
 To: zhao.huab...@zte.com.cn kanagaraj.manic...@huawei.com
 Cc: onap-discuss@lists.onap.org
 Subject: Re: [onap-discuss] [OOM][MSB][Integration] OOM MSB 
Integrationfinished 




 


Hi,


To Shed a little bit of light on that. That is created from the aai credentials 
that can be found in the robot script.


In postman, if you select basic auth and enter the credentials, you can see 
that this header gets added to your requests.


Regards


Arul


 


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhao.huab...@zte.com.cn
 Sent: Tuesday, September 5, 2017 10:37 PM
 To: kanagaraj.manic...@huawei.com
 Cc: onap-discuss@lists.onap.org
 Subject: Re: [onap-discuss] [OOM][MSB][Integration] OOM MSB 
Integrationfinished 


 

If I understand correctly, For authentication with AAI, you need to add an 
authentication header in the http request like this

Authorization:Basic QUFJOkFBSQ==

 

 



Original Mail



Sender: zhaohuabing10201488



To:  



CC:   



Date: 2017/09/06 10:20



Subject: Re:RE: Re:RE: [onap-discuss] [OOM][MSB][Integration] OOM MSB 
Integrationfinished 




 

Sorry, There is a minor mistake in the previous response.

 

Then, you could use 
http://{msb_iag_ip}:{msb_iag_port}/aai-cloudInfrastructure/v11/cloude-regions 
to  access it

The url should be  
http://{msb_iag_ip}:{msb_iag_port}/api/aai-cloudInfrastructure/v11/cloude-regions
 

The standard URL format is http://[host]:[port]/api/{service name}]/v{version  
number}/{resource}, api  is missing in the previous response.

 


 



 



Sender: zhaohuabing10201488



To:  



CC:   



Date: 2017/09/06 09:59



Subject: Re:RE: Re:RE: [onap-discuss] [OOM][MSB][Integration] OOM MSB 
Integrationfinished 




 

 

 



Sender:  



To: zhaohuabing10201488



CC:   



Date: 2017/09/05 18:30



Subject: RE: Re:RE: [onap-discuss] [OOM][MSB][Integration] OOM MSB 
Integrationfinished 




 


Hi Huabing,


 


For example, to see the cloud details from aai, it provides the api 
/aai/v11/cloud-infrastructure/cloude-regions


So access this URI via MSB, should I use  
http://{msb_iag_ip}:{msb_iag_port}/aai-cloudInfrastructure/v1/aai/v11/cloud-infrastructure/cloude-regions


It seems that the /aai/v11 part is missing from the registration info.


For the version, I think we should align to v11.


I will modify the registration info to 

{

  "serviceName": "aai-cloudInfrastructure",

  "version": "v11",

  "url": "/aai/v11/cloud-infrastructure",

  "protocol": "REST",

  "port": "8443",

  "enable_ssl":"True",

  "visualRange":"1"

  }


 


Then, you could use 
http://{msb_iag_ip}:{msb_iag_port}/aai-cloudInfrastructure/v11/cloude-regions 
to  access it


 


If so, then there are 2 different versions present v1 and v11 and two times 
service name presents aai  and aai-cloudInfrastructure.


I think this is not right. And the same problem will occur for every service.


 


OR from CLI, I could use 
http://{msb_iag_ip}:{msb_iag_port}/aai-cloudInfrastructure/v1/cloud-infrastructure/cloude-regions
   and MSB will redirect this


To AAI with 
http://{aai_ip}:{aai_port}/aai/v11/cloud-infrastructure/cloude-regions   ?


 


Kindly help.


 


Also there is another problem. Every service in ONAP uses its own basic 
authentication  and there is  no common user management


Across services to use with REST API. So How does MSB maintains the credentials 
and every service.


The simple answer is MSB doesn't maintain the credentials for 

Re: [onap-discuss] [OOM][MSB][Integration] OOM MSB Integrationfinished

[zhao.huabing]

Hi Kanagaraj,






AAI group the APIs into multiple "tags" under one port 8443, including


cloudInfrastructure


business


search


actions


service-design-and-creation


network


esr






Currently, these different tags have been mapped to different service name 
inside MSB. So we need  tag name like aai-cloudInfrastructure to differentiate 
these microservices.


Otherwise, we have to take the group tag as part of the resource url and only 
register one service name for aai.






I suggest that different group tag should be mapped to different service 
because I guess the initial intention of group of AAI APIs is to group APIs for 
different purpose.






@Jimmy, what's your preference as the AAI PTL?






Here is the service list provided by AAI.



https://wiki.onap.org/download/attachments/13598793/aai_swagger_v11.html?api=v2


https://wiki.onap.org/display/DW/ONAP+Services+List#ONAPServicesList-A 






Thanks,


Huabing








Original Mail



Sender:  
To: zhaohuabing10201488
CC:   
Date: 2017/09/06 13:00
Subject: RE: Re:RE: Re:RE: [onap-discuss] [OOM][MSB][Integration] OOM MSB 
Integrationfinished 







Dear Huabing,


 


For registering, it should be


 

{

  "serviceName": "aai-cloudInfrastructure",

  "version": "v11",

  "url": "/aai/v11/cloud-infrastructure",

  "protocol": "REST",

  "port": "8443",

  "enable_ssl":"True",

  "visualRange":"1"

  }


Then it should be ok, url should be having only the root-context and 
cloud-infrastructure should be removed from it.


 


For the authentication, yes, clients should to authentication with respective 
services and there is no common auth model exist so far (AAF).


Regarding this, I will send a separate mail to get the decision point on how 
the user model will be supported in amesterdam release.


 


Thanks


Kanagaraj M


 


 


***
 
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**
 
 
***
 This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
 
***


 



From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn] 
 Sent: Wednesday, September 06, 2017 8:07 AM
 To: Kanagaraj Manickam
 Cc: frank.obr...@amdocs.com onap-discuss@lists.onap.org
 Subject: Re:RE: Re:RE: [onap-discuss] [OOM][MSB][Integration] OOM MSB 
Integrationfinished 



 

If I understand correctly, For authentication with AAI, you need to add an 
authentication header in the http request like this

Authorization:Basic QUFJOkFBSQ==

 

 



Original Mail



Sender: zhaohuabing10201488



To:  



CC:   



Date: 2017/09/06 10:20



Subject: Re:RE: Re:RE: [onap-discuss] [OOM][MSB][Integration] OOM MSB 
Integrationfinished 




 

Sorry, There is a minor mistake in the previous response.

 

Then, you could use 
http://{msb_iag_ip}:{msb_iag_port}/aai-cloudInfrastructure/v11/cloude-regions 
to  access it

The url should be  
http://{msb_iag_ip}:{msb_iag_port}/api/aai-cloudInfrastructure/v11/cloude-regions
 

The standard URL format is http://[host]:[port]/api/{service name}]/v{version  
number}/{resource}, api  is missing in the previous response.

 


 



 



Sender: zhaohuabing10201488



To:  



CC:   



Date: 2017/09/06 09:59



Subject: Re:RE: Re:RE: [onap-discuss] [OOM][MSB][Integration] OOM MSB 
Integrationfinished 




 

 

 



Sender:  



To: zhaohuabing10201488



CC:   



Date: 2017/09/05 18:30



Subject: RE: Re:RE: [onap-discuss] [OOM][MSB][Integration] OOM MSB 
Integrationfinished 




 


Hi Huabing,


 


For example, to see the cloud details from aai, it provides the api 
/aai/v11/cloud-infrastructure/cloude-regions


So access this URI via MSB, should I use  
http://{msb_iag_ip}:{msb_iag_port}/aai-cloudInfrastructure/v1/aai/v11/cloud-infrastructure/cloude-regions


It seems that the /aai/v11 part is missing from the 

Re: [onap-discuss] [OOM][MSB][Integration] OOM MSB Integrationfinished

[zhao.huabing]

If I understand correctly, For authentication with AAI, you need to add an 
authentication header in the http request like this

Authorization:Basic QUFJOkFBSQ==










Original Mail



Sender: zhaohuabing10201488
To:  
CC:   
Date: 2017/09/06 10:20
Subject: Re:RE: Re:RE: [onap-discuss] [OOM][MSB][Integration] OOM MSB 
Integrationfinished 








Sorry, There is a minor mistake in the previous response.






Then, you could use 
http://{msb_iag_ip}:{msb_iag_port}/aai-cloudInfrastructure/v11/cloude-regions 
to access it


The url should be  
http://{msb_iag_ip}:{msb_iag_port}/api/aai-cloudInfrastructure/v11/cloude-regions
 


The standard URL format is http://[host]:[port]/api/{service name}]/v{version  
number}/{resource}, api is missing in the previous response.

















Sender: zhaohuabing10201488
To:  
CC:   
Date: 2017/09/06 09:59
Subject: Re:RE: Re:RE: [onap-discuss] [OOM][MSB][Integration] OOM MSB 
Integrationfinished 














Sender:  
To: zhaohuabing10201488
CC:   
Date: 2017/09/05 18:30
Subject: RE: Re:RE: [onap-discuss] [OOM][MSB][Integration] OOM MSB 
Integrationfinished 







Hi Huabing,


 


For example, to see the cloud details from aai, it provides the api 
/aai/v11/cloud-infrastructure/cloude-regions


So access this URI via MSB, should I use  
http://{msb_iag_ip}:{msb_iag_port}/aai-cloudInfrastructure/v1/aai/v11/cloud-infrastructure/cloude-regions


It seems that the /aai/v11 part is missing from the registration info.


For the version, I think we should align to v11.


I will modify the registration info to 


{


  "serviceName": "aai-cloudInfrastructure",


  "version": "v11",


  "url": "/aai/v11/cloud-infrastructure",


  "protocol": "REST",


  "port": "8443",


  "enable_ssl":"True",


  "visualRange":"1"


  }






Then, you could use 
http://{msb_iag_ip}:{msb_iag_port}/aai-cloudInfrastructure/v11/cloude-regions 
to access it






If so, then there are 2 different versions present v1 and v11 and two times 
service name presents aai and aai-cloudInfrastructure.


I think this is not right. And the same problem will occur for every service.


 


OR from CLI, I could use 
http://{msb_iag_ip}:{msb_iag_port}/aai-cloudInfrastructure/v1/cloud-infrastructure/cloude-regions
  and MSB will redirect this


To AAI with 
http://{aai_ip}:{aai_port}/aai/v11/cloud-infrastructure/cloude-regions  ?


 


Kindly help.


 


Also there is another problem. Every service in ONAP uses its own basic 
authentication  and there is no common user management


Across services to use with REST API. So How does MSB maintains the credentials 
and every service.


The simple answer is MSB doesn't maintain the credentials for every service, if 
the service need authentication before access, the clients needs to go through 
the authentication process themselves. For long term, MSB propose to use API 
Gateway as the entry point for central authentication, to achieve that, we need 
to reach consensus with the overall security Architecture first and MSB need to 
integrate with AAF. Indivial projects also need to modify their codes. I don't 
think we can achieve that in Amsterdam.  


 


Thank you.


 


Regards


Kanagaraj M


 


***
 
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**
 
 
***
 This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
 
***


 



From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn] 
 Sent: Tuesday, September 05, 2017 2:01 PM
 To: Kanagaraj Manickam
 Cc: frank.obr...@amdocs.com onap-discuss@lists.onap.org
 Subject: Re:RE: [onap-discuss] [OOM][MSB][Integration] OOM MSB 
Integrationfinished 



 

Hi Kanagaraj,

 

The microservie endpoint url is a standard format 
http://[host]:[port]/api/{service name}]/v{version  number}/{resource}

Regarding your question, MSB only need the  http://[host]:[port]/api/{service 

Re: [onap-discuss] [OOM][MSB][Integration] OOM MSB Integrationfinished

[zhao.huabing]

Sorry, There is a minor mistake in the previous response.






Then, you could use 
http://{msb_iag_ip}:{msb_iag_port}/aai-cloudInfrastructure/v11/cloude-regions 
to access it


The url should be  
http://{msb_iag_ip}:{msb_iag_port}/api/aai-cloudInfrastructure/v11/cloude-regions
 


The standard URL format is http://[host]:[port]/api/{service name}]/v{version  
number}/{resource}, api is missing in the previous response.








Original Mail



Sender: zhaohuabing10201488
To:  
CC:   
Date: 2017/09/06 09:59
Subject: Re:RE: Re:RE: [onap-discuss] [OOM][MSB][Integration] OOM MSB 
Integrationfinished 














Sender:  
To: zhaohuabing10201488
CC:   
Date: 2017/09/05 18:30
Subject: RE: Re:RE: [onap-discuss] [OOM][MSB][Integration] OOM MSB 
Integrationfinished 







Hi Huabing,


 


For example, to see the cloud details from aai, it provides the api 
/aai/v11/cloud-infrastructure/cloude-regions


So access this URI via MSB, should I use  
http://{msb_iag_ip}:{msb_iag_port}/aai-cloudInfrastructure/v1/aai/v11/cloud-infrastructure/cloude-regions


It seems that the /aai/v11 part is missing from the registration info.


For the version, I think we should align to v11.


I will modify the registration info to 


{


  "serviceName": "aai-cloudInfrastructure",


  "version": "v11",


  "url": "/aai/v11/cloud-infrastructure",


  "protocol": "REST",


  "port": "8443",


  "enable_ssl":"True",


  "visualRange":"1"


  }






Then, you could use 
http://{msb_iag_ip}:{msb_iag_port}/aai-cloudInfrastructure/v11/cloude-regions 
to access it






If so, then there are 2 different versions present v1 and v11 and two times 
service name presents aai and aai-cloudInfrastructure.


I think this is not right. And the same problem will occur for every service.


 


OR from CLI, I could use 
http://{msb_iag_ip}:{msb_iag_port}/aai-cloudInfrastructure/v1/cloud-infrastructure/cloude-regions
  and MSB will redirect this


To AAI with 
http://{aai_ip}:{aai_port}/aai/v11/cloud-infrastructure/cloude-regions  ?


 


Kindly help.


 


Also there is another problem. Every service in ONAP uses its own basic 
authentication  and there is no common user management


Across services to use with REST API. So How does MSB maintains the credentials 
and every service.


The simple answer is MSB doesn't maintain the credentials for every service, if 
the service need authentication before access, the clients needs to go through 
the authentication process themselves. For long term, MSB propose to use API 
Gateway as the entry point for central authentication, to achieve that, we need 
to reach consensus with the overall security Architecture first and MSB need to 
integrate with AAF. Indivial projects also need to modify their codes. I don't 
think we can achieve that in Amsterdam.  


 


Thank you.


 


Regards


Kanagaraj M


 


***
 
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**
 
 
***
 This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
 
***


 



From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn] 
 Sent: Tuesday, September 05, 2017 2:01 PM
 To: Kanagaraj Manickam
 Cc: frank.obr...@amdocs.com onap-discuss@lists.onap.org
 Subject: Re:RE: [onap-discuss] [OOM][MSB][Integration] OOM MSB 
Integrationfinished 



 

Hi Kanagaraj,

 

The microservie endpoint url is a standard format 
http://[host]:[port]/api/{service name}]/v{version  number}/{resource}

Regarding your question, MSB only need the  http://[host]:[port]/api/{service 
name}]/v{version number} part for service registration and request  routing. 
{resource} part is what resource the consumer want to 
create/retrieve/update/delete and MSB just pass it transparently to service 
provider.

 

There're two approaches  to access the individual services by leveraging MSB.

 

MSB Java SDK(aka Client side discovery): the example codes can be found here: 

Re: [onap-discuss] [OOM][MSB][Integration] OOM MSB Integrationfinished

[zhao.huabing]

Hi Michael,

We need to bring up msb and registrator before other containers. 

I'm trying to deploy AAI in kubernetes cluster, If AAI can be deployed 
successfully I can show an example calling AAI service, otherwise I will use an 
simple mock service.

Thanks,

Huabing











Original Mail



Sender:  
To: zhaohuabing10201488
CC:  
Date: 2017/09/04 22:30
Subject: RE: [onap-discuss] [OOM][MSB][Integration] OOM MSB Integrationfinished







Huabing,


   Very nice work, I personally would be interested in seeing how other 
services communicate to AAI via V11 calls for example. Bringing up the new 4 
onap-msb  containers for a look now (I see we need to add them to the root of 
the dependency tree) – before the other 44.


   Looking forward to the demo at the OOM meeting on Wed at 2300h CST / 1100h 
EDT


   /michael


 


 


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhao.huab...@zte.com.cn
 Sent: Sunday, September 3, 2017 21:26
 To: david.sauvag...@bell.ca Mike Elliott  Roger 
Maitland 
 Cc: onap-discuss@lists.onap.org
 Subject: [onap-discuss] [OOM][MSB][Integration] OOM MSB Integration finished


 

Hi David and OOM Team,


 


I'm glad to let you know that oom registrator has been successfully deployed in 
k8s cluster which filled the last part of map. Now every ONAP microservices 
deployed by OOM will be automatically registered to MSB  by oom registrator, 
and microservices can leverage MSB SDK or API Gateway to communicate with each 
other easily.


 


I could show the demo in this week's meeting if we have time, it will cost 
about 5 minutes.


 


I'd also like to discuss some minor issues like how to start MSB and 
registrator first in the OOM script so they're ready when other onap 
Microservices are spun up by OOM.


 


Cheers,


Huabing



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] [OOM][MSB][Integration] OOM MSB Integrationfinished

[zhao.huabing]

Hi Kanagaraj,






The microservie endpoint url is a standard format 
http://[host]:[port]/api/{service name}]/v{version number}/{resource}


Regarding your question, MSB only need the  http://[host]:[port]/api/{service 
name}]/v{version number} part for service registration and request routing. 
{resource} part is what resource the consumer want to 
create/retrieve/update/delete and MSB just pass it transparently to service 
provider.






There're two approaches  to access the individual services by leveraging MSB.






MSB Java SDK(aka Client side discovery): the example codes can be found here: 

https://gerrit.onap.org/r/gitweb?p=msb/java-sdk.gita=treef=exampleh=1c331f86cbcbdb8cc2935d8ac41169da1a523ec5hb=refs/heads/master
 




MSB API Gateway(aka Server side discovery), CLI just need to send the request 
to MSB API Gateway(Internal API Gateway for CLI).




For example, the service definition of AAI coludInfrastructure microservice is

{

  "serviceName": "aai-cloudInfrastructure",

  "version": "v1",

  "url": "/cloud-infrastructure",

  "protocol": "REST",

  "port": "8443",

  "enable_ssl":"True",

  "visualRange":"1"

  }




Access the service 
http://{msb_iag_ip}:{msb_iag_port}/aai-cloudInfrastructure/v1/{resource}




Here are the slides I presented and the recording at the MSB tutorial session 
in case you need more details: 
https://wiki.onap.org/display/DW/MSB+Tutorial-2017-08-23




Thanks,

Huabing











Original Mail



Sender:  
To:  zhaohuabing10201488
CC:  
Date: 2017/09/05 15:27
Subject: RE: [onap-discuss] [OOM][MSB][Integration] OOM MSB Integrationfinished







Dear Huabing and Michael,


 


CLI has dependency on the MSB to discover the service before issuing the 
commands to that service.


I believe this OOM and MSB integration will compliment CLI and thank you.  And 
I have a question related to it, kindly help:


 


When OOM register the service in to MSB, what the is the format of Service URL 
followed ?


For example, every service has URL in the form of 
://:/


In this format, when OOM register the service, what portion of this service URL 
will be used?


Here, CLI would look for the ://: from MSB as base 
path.


 


Thanks


Kanagaraj M


 


***
 
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**
 
 
***
 This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
 
***



 



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Michael O'Brien
 Sent: Monday, September 04, 2017 8:00 PM
 To: zhao.huab...@zte.com.cn
 Cc: onap-discuss@lists.onap.org
 Subject: Re: [onap-discuss] [OOM][MSB][Integration] OOM MSB Integration 
finished




 


Huabing,


   Very nice work, I personally would be interested in seeing how other 
services communicate to AAI via V11 calls for example. Bringing up the new 4 
onap-msb  containers for a look now (I see we need to add them to the root of 
the dependency tree) – before the other 44.


   Looking forward to the demo at the OOM meeting on Wed at 2300h CST / 1100h 
EDT


   /michael


 


 


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhao.huab...@zte.com.cn
 Sent: Sunday, September 3, 2017 21:26
 To: david.sauvag...@bell.ca Mike Elliott  Roger 
Maitland 
 Cc: onap-discuss@lists.onap.org
 Subject: [onap-discuss] [OOM][MSB][Integration] OOM MSB Integration finished


 

Hi David and OOM Team,


 


I'm glad to let you know that oom registrator has been successfully deployed in 
k8s cluster which filled the last part of map. Now every ONAP microservices 
deployed by OOM will be automatically registered to MSB  by oom registrator, 
and microservices can leverage MSB SDK or API Gateway to communicate with each 
other easily.


 


I could show the demo in this week's meeting if we have time, it will cost 
about 5 minutes.


 


I'd also like to discuss some minor issues like how to start MSB and 

[onap-discuss] [OOM][MSB][Integration] OOM MSB Integration finished

[zhao.huabing]

Hi David and OOM Team,






I'm glad to let you know that oom registrator has been successfully deployed in 
k8s cluster which filled the last part of map. Now every ONAP microservices 
deployed by OOM will be automatically registered to MSB by oom registrator, and 
microservices can leverage MSB SDK or API Gateway to communicate with each 
other easily.





I could show the demo in this week's meeting if we have time, it will cost 
about 5 minutes.





I'd also like to discuss some minor issues like how to start MSB and 
registrator first in the OOM script so they're ready when other onap 
Microservices are spun up by OOM.





Cheers,


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

[onap-discuss] Jenkins job failed due to Sonar 500 Error

[zhao.huabing]

Hi,

A couple of jenkis job failed due to an 500 Error when trying to access sonar. 
Could you please help on this issue?




11:33:28 [ERROR] Failed to execute goal 
org.sonarsource.scanner.maven:sonar-maven-plugin:3.2:sonar (default-cli) on 
project msb-discovery-parent: Unable to load component class 
org.sonar.batch.report.ActiveRulesPublisher: Unable to load component interface 
org.sonar.api.batch.rule.ActiveRules: Unable to load component class 
org.sonar.batch.rule.ModuleQProfiles: Error 500 on 
https://sonar.onap.org/api/qualityprofiles/search.protobuf?projectKey=org.onap.msb.discovery%3Amsb-discovery-parent
 -> [Help 1]11:33:28 [ERROR] 
11:33:28 [ERROR] To see the full stack trace of the errors, re-run Maven with 
the -e switch.11:33:28 [ERROR] Re-run Maven using the -X switch to enable full 
debug logging.11:33:28 [ERROR] 
11:33:28 [ERROR] For more information about the errors and possible solutions, 
please read the following articles:11:33:28 [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException11:33:28 
Build step 'Invoke top-level Maven targets' marked build as failurefull log can 
be found here

 
https://jenkins.onap.org/view/msb/job/msb-discovery-master-release-version-java-daily/53/console
 

https://jenkins.onap.org/view/msb/job/msb-swagger-sdk-master-release-version-java-daily/4/console







Thanks,

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

[onap-discuss] msb-apigateway-master-stage-site-java jenkins job failed

[zhao.huabing]

Hi 





Some of MSB jenkins job failed due to a 504 Gateway Time-out error. It seems 
that ONAP Jenkins server is not stable these days, could you please take a look 
at it?





This is the error message:

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.6:site (default-cli) on project 
msb-apigateway-parent: failed to get report for 
org.apache.maven.plugins:maven-javadoc-plugin: Failed to execute goal on 
project apiroute-service: Could not resolve dependencies for project 
org.onap.msb.apigateway.apiroute:apiroute-service:jar:1.0.0: Failed to collect 
dependencies at io.dropwizard:dropwizard-core:jar:0.8.0 -> 
io.dropwizard:dropwizard-validation:jar:0.8.0 -> 
org.hibernate:hibernate-validator:jar:5.1.3.Final: Failed to read artifact 
descriptor for org.hibernate:hibernate-validator:jar:5.1.3.Final: Could not 
transfer artifact org.jboss.arquillian:arquillian-bom:pom:1.0.2.Final from/to 
staging (https://nexus.onap.org/content/repositories/staging/): Failed to 
transfer file: 
https://nexus.onap.org/content/repositories/staging/org/jboss/arquillian/arquillian-bom/1.0.2.Final/arquillian-bom-1.0.2.Final.pom.
 Return code is: 504 , ReasonPhrase:Gateway Time-out. -> [Help 1]13:23:51 
[ERROR] 
13:23:51 [ERROR] To see the full stack trace of the errors, re-run Maven with 
the -e switch.13:23:51 [ERROR] Re-run Maven using the -X switch to enable full 
debug logging.13:23:51 [ERROR] 
13:23:51 [ERROR] For more information about the errors and possible solutions, 
please read the following articles:The full log is 
here:https://jenkins.onap.org/view/msb/job/msb-apigateway-master-stage-site-java/
 




Thanks,

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

Re: [onap-discuss] Help: Which jjb template can be used for Go?

[zhao.huabing]

Hi Jess, Andrew,

Sorry for the direct connection, It's kind of an urgent issue, could you kindly 
help with this?

Thanks,

Huabing











Original Mail



Sender: zhaohuabing10201488
To:  
CC:  
Date: 2017/08/31 15:12
Subject: [onap-discuss] Help: Which jjb template can be used for Go?







Hi,

I'm working on jenkins jobs(verify, merge, daily and docker image) for 
oom/registrator which is written in Go language.  Which jjb templates am I 
supposed to use? There are a lot of templates in ci-management repo, but I 
can't find a suitable one for Go by myself. 





We might need these templates:

Verify job:  which can trigger a shell script to build Go binaries

Merge job: which can  trigger a shell script to build Go binaries

Daily job: which can  trigger a shell script to build Go binaries

Docker job: which can  trigger a shell script to build docker image




We also need a Jenkins work node which has Go installed to run the jobs.




I think we don't need to push the executable binaries to nexus which is used 
for java lib, only the docker image will be push to nexus3. So we might not 
need the daily job template.




Could you please help with this?




Thanks,


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

[onap-discuss] Help: Which jjb template can be used for Go?

[zhao.huabing]

Hi,

I'm working on jenkins jobs(verify, merge, daily and docker image) for 
oom/registrator which is written in Go language.  Which jjb templates am I 
supposed to use? There are a lot of templates in ci-management repo, but I 
can't find a suitable one for Go by myself. 





We might need these templates:

Verify job:  which can trigger a shell script to build Go binaries

Merge job: which can  trigger a shell script to build Go binaries

Daily job: which can  trigger a shell script to build Go binaries

Docker job: which can  trigger a shell script to build docker image




We also need a Jenkins work node which has Go installed to run the jobs.




I think we don't need to push the executable binaries to nexus which is used 
for java lib, only the docker image will be push to nexus3. So we might not 
need the daily job template.




Could you please help with this?




Thanks,


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

Re: [onap-discuss] [msb] [integration][vnfsdk] Daily build failing due tosome banned dependencies.

[zhao.huabing]

Hi Gary,




We're facing similar issues

msb-discovery-master-docker-java-version-shell-dailyDownloaded: 
https://nexus.onap.org/content/repositories/public/org/apache/maven/maven-compat/3.0/maven-compat-3.0.jar
 (279 KB at 464.5 KB/sec)
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireReleaseDeps failed 
with message:
Found Banned Dependency: 
org.onap.oparent:version-check-maven-plugin:jar:1.0.0-SNAPSHOT
Use 'mvn dependency:tree' to locate the source of the banned dependencies.


msb-apigateway-master-docker-java-version-shell-daily12:54:17 [WARNING] Rule 0: 
org.apache.maven.plugins.enforcer.RequireReleaseDeps failed with 
message:12:54:17 Found Banned Dependency: 
org.onap.oparent:version-check-maven-plugin:jar:1.0.0-SNAPSHOT12:54:17 Use 'mvn 
dependency:tree' to locate the source of the banned dependencies.


msb-discovery-master-release-version-java-daily[INFO] --- 
maven-enforcer-plugin:3.0.0-M1:enforce (enforce-no-snapshots) @ 
msb-discovery-parent ---
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireReleaseDeps failed 
with message:
Found Banned Dependency: 
org.onap.oparent:version-check-maven-plugin:jar:1.0.0-SNAPSHOT
Use 'mvn dependency:tree' to locate the source of the banned 
dependencies.msb-swagger-sdk-master-release-version-java-daily[INFO] --- 
maven-enforcer-plugin:3.0.0-M1:enforce (enforce-no-snapshots) @ swagger-sdk ---
[WARNING] The artifact org.apache.commons:commons-io:jar:1.3.2 has been 
relocated to commons-io:commons-io:jar:1.3.2
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireReleaseDeps failed 
with message:
Found Banned Dependency: 
org.onap.oparent:version-check-maven-plugin:jar:1.0.0-SNAPSHOT
Use 'mvn dependency:tree' to locate the source of the banned dependencies.




There is also another issue rising says "Failed to download dependencies"

Project msb-apigateway-master-stage-site-javaFailed to download 
dependenciesProject org.onap.msb.apigateway.apiroute:apiroute-service:jar:1.0.0 
could not be built, as one of its dependency chain, 
io.dropwizard:dropwizard-core:jar:0.8.0 -> 
io.dropwizard:dropwizard-validation:jar:0.8.0 -> 
org.hibernate:hibernate-validator:jar:5.1.3.Final: Failed to read artifact 
descriptor for org.hibernate:hibernate-validator:jar:5.1.3.Final failed to 
resolve, because we could not download artifact { 
org.onap.msb.apigateway.apiroute:apiroute-service:jar:1.0.0,3} from repository 
{ org.onap.msb.apigateway.apiroute:apiroute-service:jar:1.0.0,4}. Reported 
cause was: 504 , ReasonPhrase:Gateway Time-out..Thanks,

Huabing




Original Mail



Sender:  
To:  
CC:  
Date: 2017/08/31 05:59
Subject: Re: [onap-discuss] [integration][vnfsdk] Daily build failing due 
tosome banned dependencies.







Hi Skip,


 


The short answer is no later than RC0 (Sept. 28th).


 


The long answer is that it may depend on the rollout schedule of 
https://wiki.onap.org/display/DW/Independent+Versioning+and+Release+Process, 
which I will introduce to the community shortly.


 


Thanks,


Gary


 


 



From: WONNELL, SKIP [mailto:kw5...@att.com] 
 Sent: Wednesday, August 30, 2017 1:39 PM
 To: Gary Wu 
 Cc: onap-discuss@lists.onap.org
 Subject: RE: [onap-discuss] [integration][vnfsdk] Daily build failing due to 
some banned dependencies.




 


Thanks Gary,


 


What is the schedule for reverting the checks back to errors?


 


Skip


 


 



From: Gary Wu [mailto:gary.i...@huawei.com] 
 Sent: Wednesday, August 30, 2017 3:27 PM
 To: WONNELL, SKIP 
 Cc: onap-discuss@lists.onap.org
 Subject: RE: [onap-discuss] [integration][vnfsdk] Daily build failing due to 
some banned dependencies.




 


Hi Skip,


 


I’ve changed the enforcer checks to just warnings now, and your job has 
completed successfully.


 


Thanks,


Gary


 



From: WONNELL, SKIP [mailto:kw5...@att.com] 
 Sent: Wednesday, August 30, 2017 12:22 PM
 To: Gary Wu 
 Subject: RE: [onap-discuss] [integration][vnfsdk] Daily build failing due to 
some banned dependencies.




 


Hi Gary,


 


We continue to see a similar issue in the APPC daily release build:  
https://jenkins..onap.org/job/appc-master-release-version-java-daily/189/


 


13:45:58 [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce 
(enforce-no-snapshots) @ appc-common ---


13:45:58 [WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireReleaseDeps 
failed with message:


13:45:58 Found Banned Dependency: 
org.openecomp.sdnc.core:dblib-provider:jar:1.1.2-SNAPSHOT


13:45:58 Use 'mvn dependency:tree' to locate the source of the banned 
dependencies.


13:45:58 [INFO] 



13:45:58 [INFO] 



13:45:58 [INFO] Skipping APP-C


13:45:58 [INFO] This project has been banned from the build due to previous 
failures.


13:45:58 [INFO] 

[onap-discuss] Reply：Re: Can't pull tiller image //Re: [OOM] Using Helmfor kubernetes deployment

[zhao.huabing]

It's fixed now.



Thanks,

Huabing






 

 Original Message 
 
 
 
 
 
 
 
 
 
 From:MikeElliott 
 
 
 
 To:zhaohuabing10201488 
 
 
 
 Cc:Borislav glozmanonap-disc...@lists.onap.org 
 
 
 
 Date:2017-08-30 20:43:34 
 
 
 
 Subject:Re: [onap-discuss] Can't pull tiller image //Re: [OOM] Using Helmfor 
kubernetes deployment 
 
 
 
 
 
 
 

 
 
 
 
 
 Hi Huabing, 
 
 
 
 
 
 
 
 
 
 Do you have Helm (along with kubectl installed on your client machine? How did 
you install helm? 
 
 
 
 
 
 
 
 
 
 Here is an example from the oom wiki 
https://wiki.onap.org/display/DW/ONAP+on+Kubernetes#ONAPonKubernetes-QuickstartInstallation
 
 
 
 
 
 
 
 
 
 
 wget http: 
 //storage.googleapis.com/kubernetes-helm/helm-v2..3.0-linux-amd64.tar.gz 
 
 
 
 
 tar -zxvf helm-v2. 
 3.0 
 -linux-amd64.tar.gz 
 
 
 
 
 mv linux-amd64/helm /usr/local/bin/helm 
 
 
 
 
 
 
 
 
 
 

 Mike. 
 
 
 
 
 
 
 
 
 
 
 

 On Aug 29, 2017, at 11:57 PM, 
 zhao.huab...@zte.com.cn wrote: 
 
 
 
 
 
 
 
 
 
 
Hi there,

 
 
 

 
 
I have successfully installed kubernetes with rancher to test using chart to 
deploy MSB. According to the instruction of rancher, I'm using docker 1.12.3 
which is the only docker version which support kubernetes.. 
http://rancher.com/docs/rancher/v1.6/en/hosts/#supported-docker-versions. 

 
 
However, Helm doesn't work. It turns out Tiller has not been spun up by 
kubernetes due to  "ImagePullBackOff" error.

 
 
When trying to manually pull the image "gcr.io/kubernetes-helm/tiller:v2.3.0", 
I got this error:

 
 
Error: Status 405 trying to pull repository kubernetes-helm/tiller: "v1 
Registry API is disabled. If you are not explicitly using the v1 Registry API, 
it is possible your v2 image could not be found. Verify that your image is 
available, or retry with `dockerd --disable-legacy-registry`. See 
https://cloud.google.com/container-registry/docs/support/deprecation-notices; 

 
 
 

 
 
It seems that tiller image can't be pulled because the version of docker 
version is too old.

 
 
 

 
 
Do you have any idea how to solve this issue?

 
 
 

 
 
Thanks,

 
 
Huabing

 
 
 

 
 
 

 
 
 

 
 
 

 
 
 

 
 
 

 
 
 
 
 
 
 
 
 

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

 
 
 
 
 
 
 
 
 
 Sender:  
  
 
 
 
 
 To:  
  
 
 
 
 
 Date:  
 2017/08/16 23:54 
 
 
 
 
 Subject:  
 [onap-discuss]  [OOM] Using Helm for kubernetes deployment 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
Hi, 
 

 
 
 
 
   
 

 
 
We did and presented a POC on the weekly OOM meeting of using Helm Charts to 
parametrize and deploy ONAP in Kubernetes. 
 

 
 
We would like to start with parametrization of docker images in the deployment 
yaml files in order to enable easy usage of different versions of the images. 
 

 
 
We would like to push this change to the OOM Gerrit. 
 

 
 
 
 
   
 

 
 
Please take a look at Helm Chart description: 
 

 
 
https://docs.helm.sh/developing_charts/#charts 
 

 
 
https://docs.helm.sh/using_helm/#quickstart-guide 
 

 
 
 
 
   
 

 
 
Please let me know if you have any concern. 
 

 
 
 
 
   
 

 
 
Thanks, 
 

 
 
Borislav Glozman 
 

 
 
O:+972.9.776.1988 
 

 
 
M:+972.52.2835726 
 

 
 
 
 
   
 

 
 
 
 

 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] [DMaaP][oom] DMaaP Deployment using OOM

[zhao.huabing]

One more thing,

In case that you're not familiar with kubernetes concepts before, these two 
links might be useful to understand the deployment and service configuration 
files which you need to provide to OOM.




https://kubernetes.io/docs/concepts/workloads/controllers/deployment/ 

https://kubernetes.io/docs/concepts/services-networking/service/ 




Thanks,

Huabing







Original Mail



Sender: zhaohuabing10201488
To:  
CC:     
   

Date: 2017/08/30 14:02
Subject: Re: [onap-discuss] [DMaaP][oom] DMaaP Deployment using OOM







Hi Varun,





I see that there is a guide on this wiki page: 
https://wiki.onap.org/display/DW/OOM+Configuration+Management 




Actually the process to deploy your project is very simple and straitforward as 
long as you understand the kubernetes concepts such as pods and service and 
have a kubernetes cluster to test it. It's mainly two YAML configuration files, 
one for kubernetes pods object and one for service object.




For me, when deploying MSB with OOM, most of the time is used to install the 
kubernetes and test the configuration files in kubernetes cluster. I recommend 
to use rancher to install the kubernetes cluster if you want to test your yaml 
configuration files, it's easier than install the kubernetes cluster yourself. 
https://github.com/rancher/rancher#installation




You can take a look at these yaml configuration files provided by other ONAP 
projects and use them as examples for your project. 

https://gerrit.onap.org/r/gitweb?p=oom.gita=treef=kubernetesh=07d2f67c15eae360e4c15595b6fd1b76d7f8ce6dhb=refs/heads/master
 




BR,

Huabing



















Sender:  
To:     

CC:    

Date: 2017/08/30 03:35
Subject: Re: [onap-discuss] [DMaaP][oom] DMaaP Deployment using OOM







Helen,


We are in early stages of understanding deployment process by OOM. I don’t have 
sufficient information to give an estimate.


 


 


 



From: Yunxia Chen [mailto:helen.c...@huawei.com] 
 Sent: Monday, August 28, 2017 6:53 PM
 To: GUDISENA, VARUNESHWAR  david.sauvag...@bell.ca HU, JUN 
NICOLAS  jerome.doucer...@bell.ca
 Cc: KOYA, RAMPRASAD  Madhur Ramachandra, R. 
 onap-discuss 
 Subject: Re: [DMaaP][oom] DMaaP Deployment using OOM




 


Hi, Varun,


 


Do you have an idea when it could be done?


 


ards,


 


Helen Chen


 



From: "GUDISENA, VARUNESHWAR" 
 Date: Monday, August 28, 2017 at 11:31 AM
 To: "david.sauvag...@bell.ca" , "HU, JUN NICOLAS" 
, "jerome.doucer...@bell.ca"  , Helen 
Chen 00725961 
 Cc: "KOYA, RAMPRASAD" , "Madhur Ramachandra, R." 
, onap-discuss 
 Subject: [DMaaP][oom] DMaaP Deployment using OOM



 


David,


I am the committer for DMaaP project. I want to deploy DMaaP using OOM. Can you 
share the resources to deploy a project using OOM.


 


Thanks


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

Re: [onap-discuss] [DMaaP][oom] DMaaP Deployment using OOM

[zhao.huabing]

Hi Varun,





I see that there is a guide on this wiki page: 
https://wiki.onap.org/display/DW/OOM+Configuration+Management 




Actually the process to deploy your project is very simple and straitforward as 
long as you understand the kubernetes concepts such as pods and service and 
have a kubernetes cluster to test it. It's mainly two YAML configuration files, 
one for kubernetes pods object and one for service object.




For me, when deploying MSB with OOM, most of the time is used to install the 
kubernetes and test the configuration files in kubernetes cluster. I recommend 
to use rancher to install the kubernetes cluster if you want to test your yaml 
configuration files, it's easier than install the kubernetes cluster yourself. 
https://github.com/rancher/rancher#installation




You can take a look at these yaml configuration files provided by other ONAP 
projects and use them as examples for your project. 

https://gerrit.onap.org/r/gitweb?p=oom.gita=treef=kubernetesh=07d2f67c15eae360e4c15595b6fd1b76d7f8ce6dhb=refs/heads/master
 




BR,

Huabing










Original Mail



Sender:  
To:     

CC:    

Date: 2017/08/30 03:35
Subject: Re: [onap-discuss] [DMaaP][oom] DMaaP Deployment using OOM







Helen,


We are in early stages of understanding deployment process by OOM. I don’t have 
sufficient information to give an estimate.


 


 


 



From: Yunxia Chen [mailto:helen.c...@huawei.com] 
 Sent: Monday, August 28, 2017 6:53 PM
 To: GUDISENA, VARUNESHWAR  david.sauvag...@bell.ca HU, JUN 
NICOLAS  jerome.doucer...@bell.ca
 Cc: KOYA, RAMPRASAD  Madhur Ramachandra, R. 
 onap-discuss 
 Subject: Re: [DMaaP][oom] DMaaP Deployment using OOM




 


Hi, Varun,


 


Do you have an idea when it could be done?


 


ards,


 


Helen Chen


 



From: "GUDISENA, VARUNESHWAR" 
 Date: Monday, August 28, 2017 at 11:31 AM
 To: "david.sauvag...@bell.ca" , "HU, JUN NICOLAS" 
, "jerome.doucer...@bell.ca"  , Helen 
Chen 00725961 
 Cc: "KOYA, RAMPRASAD" , "Madhur Ramachandra, R." 
, onap-discuss 
 Subject: [DMaaP][oom] DMaaP Deployment using OOM



 


David,


I am the committer for DMaaP project. I want to deploy DMaaP using OOM. Can you 
share the resources to deploy a project using OOM.


 


Thanks


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

[onap-discuss] Can't pull tiller image //Re: [OOM] Using Helm for kubernetes deployment

[zhao.huabing]

Hi there,




I have successfully installed kubernetes with rancher to test using chart to 
deploy MSB. According to the instruction of rancher, I'm using docker 1.12.3 
which is the only docker version which support kubernetes. 
http://rancher.com/docs/rancher/v1.6/en/hosts/#supported-docker-versions. 

However, Helm doesn't work. It turns out Tiller has not been spun up by 
kubernetes due to  "ImagePullBackOff" error.

When trying to manually pull the image "gcr.io/kubernetes-helm/tiller:v2.3.0", 
I got this error:

Error: Status 405 trying to pull repository kubernetes-helm/tiller: "v1 
Registry API is disabled. If you are not explicitly using the v1 Registry API, 
it is possible your v2 image could not be found. Verify that your image is 
available, or retry with `dockerd --disable-legacy-registry`. See 
https://cloud.google.com/container-registry/docs/support/deprecation-notices; 




It seems that tiller image can't be pulled because the version of docker 
version is too old.




Do you have any idea how to solve this issue?




Thanks,

Huabing






















Original Mail



Sender:  
To:  
Date: 2017/08/16 23:54
Subject: [onap-discuss]  [OOM] Using Helm for kubernetes deployment







Hi,


 


We did and presented a POC on the weekly OOM meeting of using Helm Charts to 
parametrize and deploy ONAP in Kubernetes.


We would like to start with parametrization of docker images in the deployment 
yaml files in order to enable easy usage of different versions of the images.


We would like to push this change to the OOM Gerrit.


 


Please take a look at Helm Chart description:


https://docs.helm.sh/developing_charts/#charts


https://docs.helm.sh/using_helm/#quickstart-guide


 


Please let me know if you have any concern.


 


Thanks,


Borislav Glozman


O:+972.9.776.1988


M:+972.52.2835726


 


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] Propose MSB Client SDK introduction at this week's A meeting

[zhao.huabing]

Great!  




Thanks,

Huabing














Original Mail



Sender:  
To: zhaohuabing10201488
CC:  
Date: 2017/08/23 21:10
Subject: RE: Propose MSB Client SDK introduction at this week's A meeting







Haubing,


 


We are starting our call @ 8 AM US/Eastern tomorrow so we will have time.  I’ll 
put you on the agenda.


 


Thanks,


jimmy


 


From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn] 
 Sent: Tuesday, August 22, 2017 9:39 PM
 To: FORSYTH, JAMES 
 Cc: onap-discuss@lists.onap.org
 Subject: Propose MSB Client SDK introduction at this week's A meeting


 

Hi Jimmy,


 


Now a Client SDK is provided to help ONAP projects leverage the service 
registration/discovery/routing/load balancing capabilities of MSB.


Can I get some time in this week's A meeting to briefly introduce the client 
SDK to the team? I will also prepare a demo to show how to use it.


 


It may take about 10 minutes.


 


Thanks,


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

Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

[zhao.huabing]

Thanks, Gray.

Besides, is it possible to move the ecomp-site configuration to Oparent POM? I 
think it's a common setting for all the project.







Original Mail



Sender:  
To: 
CC:  zhaohuabing10201488
Date: 2017/08/24 05:52
Subject: RE: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins 
job issue





Hi Huabing,

I suspect the issue is that the site ID in your distributionManagement tags is 
“onap-site”.  I believe the expected value is “ecomp-site”.

Thanks,
Gary

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhao.huab...@zte.com.cn
Sent: Tuesday, August 22, 2017 6:53 PM
To: onap-helpd...@rt.linuxfoundation.org
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins 
job issue


Hi Gary, Jessica,



This job has similar issue:

msb-apigateway-master-stage-site-java

https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/msb-apigateway-master-stage-site-java/3/console.log.gz



[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.6:stage-deploy (default-cli) on 
project msb-apigateway-parent: Error uploading site: Failed to transfer file: 
https://nexus.onap.org/content/sites/site/org/onap/msb/apigateway/1.0.0/staging/./dependencies.html.
 Return code is: 401 -> [Help 1]



Could you please help me with that?



Thanks,

Huabing
Original Mail
Sender:  
>
To:
CC:  
>zhaohuabing10201488
Date: 2017/08/22 06:39
Subject: [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue


Hi Huabing,

I've incorporated the staging plugin config below into oparent, and it looks 
like the MSB release-version jobs are completing successfully now.

Thanks,
Gary


-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Monday, August 21, 2017 3:20 PM
To: Gary Wu >
Cc: onap-discuss@lists.onap.org 
zhao.huab...@zte.com.cn
Subject: [ONAP Helpdesk #44285] RE: MSB Jenkins job issue

Sure, of course.

Basically the pom.xml needs to be containing the repositories, distribution 
management and staging plugin blocks.
Let's take the vid pom.xml as an example of the information your pom is missing.

Basically, the staging plugin definition needs to look like this:

org.sonatype.plugins

nexus-staging-maven-plugin
1.6.7
true

${nexusproxy}

176c31dfe190a
ecomp-staging




You will also need the definition for the repositories, which looks like this:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Repository

${nexusproxy}/${snapshotNexusPath}


ecomp-staging
VID Staging Repository

${nexusproxy}/${stagingNexusPath}



oss-snapshots
oss Central - Snapshots

https://oss.sonatype.org/service/local/repositories/releases/content/https://oss.sonatype.org/service/local/repositories/releases/content/%3c/url>>



Notice that the serverIDs are prefixed like "ecomp-" and not "onap-". This is a 
rename that still hasn't changed, but we are discussing about the impact on 
doing so.

Lastly, you will also need to update the distribution management:


ecomp-releases
VID Release Repository

Re: [onap-discuss] 答复：Re: [dcae]MSB Demo Presentation

[zhao.huabing]

Yes, as we discussed at the last meeting, I will present the demo.

If anything else you would like to know from DCAE or Holmes side, I can include 
in the presentation as well.











Original Mail



Sender: fuguangrong10144542
To:  
CC:  zhaohuabing10201488
Date: 2017/08/24 08:07
Subject: 答复：Re: [dcae]MSB Demo Presentation






Lusheng,

Huabing will show the demo. It'll take 10 minutes or so. 

Thanks. 

Guangrong



  











Sender: JI,LUSHENG(LUSHENG)

To: 付光荣10144542

CC: onap-discuss@lists.onap.org

Date: 2017-08-24 07:10:48

Subject: Re: [dcae]MSB Demo Presentation


  

Guangrong,


 


Thanks!  Could you please confirm that you would be able to do the MSB demo?  
And how much time do you need?


 


Thanks,


Lusheng


 



From: "fu.guangr...@zte.com.cn" 
 Date: Monday, August 21, 2017 at 6:20 AM
 To: "JI, LUSHENG (LUSHENG)" 
 Cc: "onap-discuss@lists.onap.org" 
 Subject: [dcae]MSB Demo Presentation



 



Lusheng,
 
 As we discussed last week, could you please reserve some time for the 
presentation of the demo of MSB at the weekly meeting of DCAE?
 
 Thanks.
 
 Best Regards,
 Guangrong___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Propose MSB Client SDK introduction at this week's Policymeeting

[zhao.huabing]

Hi Pam,






Thanks for your consideration, Thursday 8pm EST/Friday 8am Beijing will be OK 
for me.  


The integration will take only a couple of lines and it can save a lot of 
efforts for the developers to handle the trivial details of service discovery 
and http request coding. I think the team can get more confidence after the 
introduction and demo. 






BR,



Huabing 








Original Mail



Sender:  
To: zhaohuabing10201488
CC:  WangXinYuan10113332 
Date: 2017/08/23 15:59
Subject: Re: Propose MSB Client SDK introduction at this week's Policymeeting







I don’t think there is time today for this at our meeting. I suggest we setup a 
one-off meeting to discuss.


 


I have no doubt the MSB Client SDK is easy to use. The time consuming part will 
be how to exactly integrate it, test that integration, etc.


 


I will be on vacation next week, so perhaps we could setup a meeting to scope 
the work out sometime this week. My schedule is really full, but we can work a 
time out.


 


Suggest Thursday 8pm EST/Friday 8am Beijing (I think you folks are in Beijing).


 


Thanks,


 


Pam


 



From: "zhao.huab...@zte.com.cn" 
 Date: Tuesday, August 22, 2017 at 9:16 PM
 To: "DRAGOSH, PAMELA L (PAM)" 
 Cc: "onap-discuss@lists.onap.org" , 
"wang.xinyu...@zte.com.cn" 
 Subject: Propose MSB Client SDK introduction at this week's Policy meeting



 

Hi Pam,

 

Now a Client SDK is provided to help ONAP projects leverage the service 
registration/discovery/routing/load balancing capabilities of MSB.

Can I get some time in this week's policy meeting? I can briefly introduce the 
client SDK and present a demo to the team.

 

Thanks,

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

Re: [onap-discuss] [msb][cli] Service health status

[zhao.huabing]

Hi Kanagaraj,




MSB will not provide  APIs for Health Status and enable/disable  a given 
service in Amsterdam release.




BR,

Huabing




Original Mail



Sender:  
To:  
Date: 2017/08/22 16:36
Subject: [onap-discuss] [msb][cli] Service health status







Hi Huabing,


 


I referred the MSB API from wiki and able to identify the API for service 
management. But couldn’t get the API for Health Status and enable/disable  a 
given service.


Please let me know if these feature are planned to support in MSB/OOM?


 


Thanks


Kanagaraj M


 


***
 
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**
 
 
***
 This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
 
***___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

[zhao.huabing]

Hi Gary, Jessica,




This job has similar issue:

msb-apigateway-master-stage-site-java

https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/msb-apigateway-master-stage-site-java/3/console.log.gz
 




[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.6:stage-deploy (default-cli) on 
project msb-apigateway-parent: Error uploading site: Failed to transfer file: 
https://nexus.onap.org/content/sites/site/org/onap/msb/apigateway/1.0.0/staging/./dependencies.html.
 Return code is: 401 -> [Help 1]


Could you please help me with that?




Thanks,

Huabing




Original Mail



Sender:  
To: 
CC:  zhaohuabing10201488
Date: 2017/08/22 06:39
Subject: [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue





Hi Huabing,

I've incorporated the staging plugin config below into oparent, and it looks 
like the MSB release-version jobs are completing successfully now.  

Thanks,
Gary


-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Monday, August 21, 2017 3:20 PM
To: Gary Wu 
Cc: onap-discuss@lists.onap.org zhao.huab...@zte.com.cn
Subject: [ONAP Helpdesk #44285] RE: MSB Jenkins job issue

Sure, of course. 

Basically the pom.xml needs to be containing the repositories, distribution 
management and staging plugin blocks.
Let's take the vid pom.xml as an example of the information your pom is 
missing. 

Basically, the staging plugin definition needs to look like this:

org.sonatype.plugins

nexus-staging-maven-plugin
1.6.7
true

${nexusproxy}

176c31dfe190a
ecomp-staging

 


You will also need the definition for the repositories, which looks like this:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Repository

${nexusproxy}/${snapshotNexusPath}


ecomp-staging
VID Staging Repository

${nexusproxy}/${stagingNexusPath}



oss-snapshots
oss Central - Snapshots

https://oss.sonatype.org/service/local/repositories/releases/content/



Notice that the serverIDs are prefixed like "ecomp-" and not "onap-". This is a 
rename that still hasn't changed, but we are discussing about the impact on 
doing so. 

Lastly, you will also need to update the distribution management:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Repository

${nexusproxy}/${snapshotNexusPath}



ecomp-site
dav:${nexusproxy}${sitePath}





Please feel free to add me as reviewer to your pom.xml changes and I can help 
further. 

I hope this information helps
Thanks!
Jess___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Propose MSB Client SDK introduction at this week's A meeting

[zhao.huabing]

Hi Jimmy,






Now a Client SDK is provided to help ONAP projects leverage the service 
registration/discovery/routing/load balancing capabilities of MSB.


Can I get some time in this week's A meeting to briefly introduce the client 
SDK to the team? I will also prepare a demo to show how to use it.






It may take about 10 minutes.





Thanks,


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

Re: [onap-discuss] Propose MSB Client SDK introduction at this week's Policy meeting

[zhao.huabing]

It may take about 10 minutes.











Original Mail



Sender: zhaohuabing10201488
To:  
CC:  wangxinyuan10113332
Date: 2017/08/23 09:16
Subject: Propose MSB Client SDK introduction at this week's Policy meeting






Hi Pam,





Now a Client SDK is provided to help ONAP projects leverage the service 
registration/discovery/routing/load balancing capabilities of MSB.


Can I get some time in this week's policy meeting? I can briefly introduce the 
client SDK and present a demo to the team.




Thanks,

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

Re: [onap-discuss] [ONAP Helpdesk #44285] RE: MSB Jenkins job issue

[zhao.huabing]

Great, Thanks Jess and Gary.











Original Mail



Sender:  
To:  
CC:  zhaohuabing10201488
Date: 2017/08/22 06:46
Subject: [ONAP Helpdesk #44285] RE: MSB Jenkins job issue





Thanks so much Gary, 

Please let me know if you guys still need my help

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

Re: [onap-discuss] Question about ONAP docker registry

[zhao.huabing]

Hi Kanagaraj,




From the Jenkins log of cli-master-docker-version-java-daily, it seems like the 
job failed at the step of the deployment of org.onap.cli:cli:pom:1.0.0 
artifact, so the docker building was not triggered.




I use shell scripts instead of mvn plugin to build the docker. 

This is the jjb job definition

  - '{project-name}-{stream}-docker-java-version-shell-daily':

  docker-pom: 'pom.xml'

  mvn-goals: 'install'

  script:

!include-raw-escape: 'build-apigateway-docker-image.sh'

By using this template, I don't have to deploy artifacts to Nexus before 
building the docker image, so this problem is bypassed.




Besides, I also have this "Failed to deploy artifacts" issue at MSB daily 
building Jenkins job. 
https://jenkins.onap.org/view/msb/job/msb-apigateway-master-release-version-java-daily/

 

BR,

Huabing



















Original Mail



Sender:  
To: zhaohuabing10201488
CC:   
Date: 2017/08/21 17:43
Subject: RE: Re:RE: [onap-discuss] Question about ONAP docker registry







Hi Huabing,


 


Can you please share the steps followed for pushing msb docker images?


 


Regards


Kanagaraj M


 


***
 
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**
 
 
***
 This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
 
***


 



From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn] 
 Sent: Monday, August 21, 2017 1:47 PM
 To: Kanagaraj Manickam
 Cc: onap-helpd...@lists.onap.org onap-discuss@lists.onap.org
 Subject: Re:RE: [onap-discuss] Question about ONAP docker registry



 

Hi Kanagaraj,

Thanks for your help.

 

I'm using nexus3.onap.org:10003 as well, and I have successfully pushed the 
image to it.

https://nexus3.onap.org/#browse/search=keyword%3Dmsb:7f6379d32f8dd78f1ee9fdfbe752b3b9
 

 

BR,

Huabing

 

 



Original Mail



Sender:  



To: zhaohuabing10201488 



CC:  



Date: 2017/08/21 16:02



Subject: RE: [onap-discuss] Question about ONAP docker registry




 


Hi Huabing,


 


Recently I build the CLI docker image and as part of that I observed that 
following nexus server is used for docker  push


But CI is failing to push and trying to get help from integration/ci team to 
get it resolved.


 


nexus3.onap.org:10003


 


Regards


Kanagaraj M


 


 


***
 
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**
 
 
***
 This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
 
***


 



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhao.huab...@zte.com.cn
 Sent: Monday, August 21, 2017 12:48 PM
 To: onap-helpd...@lists.onap.org
 Cc: onap-discuss@lists.onap.org
 Subject: [onap-discuss] Question about ONAP docker registry



 

Hi,

 

I'm building the MSB docker images according to the development guides 
https://wiki.onap.org/display/DW/Docker+DevOps.   But there  is no guide about 
how to push the docker image on this page, I look at some of the existing 
docker building shell as reference. When I dig into these scripts, It turns out 
there are multiple registry like nexus3.onap.org:10001, nexus3.onap.org:10003.

 

Does anyone know the 

Re: [onap-discuss] Question about ONAP docker registry

[zhao.huabing]

Hi Kanagaraj,

Thanks for your help.




I'm using nexus3.onap.org:10003 as well, and I have successfully pushed the 
image to it.

https://nexus3.onap.org/#browse/search=keyword%3Dmsb:7f6379d32f8dd78f1ee9fdfbe752b3b9
 




BR,

Huabing










Original Mail



Sender:  
To: zhaohuabing10201488 
CC:  
Date: 2017/08/21 16:02
Subject: RE: [onap-discuss] Question about ONAP docker registry







Hi Huabing,


 


Recently I build the CLI docker image and as part of that I observed that 
following nexus server is used for docker push


But CI is failing to push and trying to get help from integration/ci team to 
get it resolved.


 


nexus3.onap.org:10003


 


Regards


Kanagaraj M


 


 


***
 
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**
 
 
***
 This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
 
***


 



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhao.huab...@zte.com.cn
 Sent: Monday, August 21, 2017 12:48 PM
 To: onap-helpd...@lists.onap.org
 Cc: onap-discuss@lists.onap.org
 Subject: [onap-discuss] Question about ONAP docker registry



 

Hi,

 

I'm building the MSB docker images according to the development guides 
https://wiki.onap.org/display/DW/Docker+DevOps.  But there  is no guide about 
how to push the docker image on this page, I look at some of the existing 
docker building shell as reference. When I dig into these scripts, It turns out 
there are multiple registry like nexus3.onap.org:10001, nexus3.onap.org:10003.

 

Does anyone know the difference of these registries and which one am I supposed 
to use to push the built image?

 

Thanks,

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

[onap-discuss] Question about ONAP docker registry

[zhao.huabing]

Hi,




I'm building the MSB docker images according to the development guides 
https://wiki.onap.org/display/DW/Docker+DevOps.  But there is no guide about 
how to push the docker image on this page, I look at some of the existing 
docker building shell as reference. When I dig into these scripts, It turns out 
there are multiple registry like nexus3.onap.org:10001, nexus3.onap.org:10003.




Does anyone know the difference of these registries and which one am I supposed 
to use to push the built image?




Thanks,

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

[onap-discuss] [MSB] MSB JAVA SDK is ready to use

[zhao.huabing]

Hi ONAP Developers and PTLs,




I'm pleased to announce that MSB JAVA SDK is provided to facilitate the point 
to point communication between ONAP Microservices now.




It's pretty simple and straightforward to use it.




First, add this dependency to your project pom file.


  


  org.onap.msb.sdk


msb-java-sdk


1.0.0-SNAPSHOT


  



Then, you can access the REST service like a normal JAVA object. MSB JAVA SDK 
takes care of service dicovery and routing for you, an it also maps the JSON 
response to a simple JAVA object, make it very handy for the developers.


String MSB_IP="127.0.0.1"

int MSB_Port=10081
 
MSBServiceClient msbClient = new MSBServiceClient(MSB_IP, MSB_Port)
 
RestServiceCreater restServiceCreater =

new RestServiceCreater(msbClient)
 
AnimalServiceClient implProxy =

restServiceCreater.createService(AnimalServiceClient.class)
 
Animal animal = implProxy.queryAnimal("panda").execute().body()

System.out.println("animal:" + animal)




An full example is also available for your reference here: 
https://gerrit.onap.org/r/gitweb?p=msb/java-sdk.gita=treef=exampleh=1c331f86cbcbdb8cc2935d8ac41169da1a523ec5hb=refs/heads/master




Currently, only JAVA SDK is provided. If you project is based on Python or you 
don't have time to switch to MSB JAVA SDK, you can still leverage MSB Internal 
API Gateway to access the services. For that, the only thing to do is send the 
request to the MSB internal API gateway IP and Port.




Besides,

If you would like to test it, please start MSB using docker first.


1. Run the Consul dockers.
sudo docker run -d --net=host --name msb_consul consul agent -dev



2. Run the MSB dockers.
sudo docker run -d --net=host --name msb_discovery zhaohuabing/msb_discovery
sudo docker run -d --net=host -e "ROUTE_LABELS=visualRange:1" --name 
internal_msb_apigateway zhaohuabing/msb_apigateway






3. Check the MSB portal to make sure everything is OK


http://127.0.0.1/msb




Cheers,

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

Re: [onap-discuss] [ONAP Helpdesk #44285] RE: MSB Jenkins job issue

[zhao.huabing]

HI Jessica,




Thanks for your response.




Could you please give me more specific instructions about how to fix this?

Am I suppose to modify the POM file of my project, the jjb file or should I 
just remove this job from jjb file because there is no official release yet?





Thanks,

Huabing








Original Mail



Sender:  
To:  
CC:  zhaohuabing10201488
Date: 2017/08/15 01:55
Subject: [ONAP Helpdesk #44285] RE: MSB Jenkins job issue





Dear Huabing and Gary, 

This daily job needs to be pushing into ecomp-staging not ecomp-releases. 
The problem is being handled correctly by Nexus since it is rejecting a re-push 
of a binary that is already been deployed here: 
https://nexus.onap.org/content/repositories/releases/org/onap/msb/apigateway/msb-apigateway-parent/1.0.0/

We need to make sure we are pushing into staging repository. 

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

Re: [onap-discuss] [integration][holmes] How to Set up a Sonar Inspection Jobj to the CI Workflow

[zhao.huabing]

+1

MSB project has the same problem.











Original Mail



Sender: FuGuangRong10144542
To:  
Date: 2017/08/14 14:07
Subject: [onap-discuss] [integration][holmes] How to Set up a Sonar Inspection 
Jobj to the CI Workflow







Hi there,




I've set up a series of Jenkins Jobs for Holmes. All of them seem to be running 
as expected. But still we could not find the Holmes related UT coverage in the 
Dashboard of ONAP Sonar.  The *-release-version-java-daily jobs have been 
removed from the workflow because it caused unknown errors and even Gary has no 
idea on how to fix them. Does it has something to do with the UT coverage?




Thanks and Regards,

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

[onap-discuss] MSB Jenkins job issue

[zhao.huabing]

Hi Gary et al,




I get this error message for the MSB Jenkins job. Do you know the possible 
reason and how to fix it?




Thanks,

Huabing




https://jenkins.onap.org/view/msb/job/msb-apigateway-master-release-version-java-daily/33/console
 




11:57:09 [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on 
project msb-apigateway-parent: Failed to deploy artifacts: Could not transfer 
artifact org.onap.msb.apigateway:msb-apigateway-parent:pom:1.0.0 from/to 
ecomp-releases (https://nexus.onap.org/content/repositories/releases): Failed 
to transfer file: 
https://nexus.onap.org/content/repositories/releases/org/onap/msb/apigateway/msb-apigateway-parent/1.0.0/msb-apigateway-parent-1.0.0.pom.
 Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]11:57:09 [ERROR] 
11:57:09 [ERROR] To see the full stack trace of the errors, re-run Maven with 
the -e switch.11:57:09 [ERROR] Re-run Maven using the -X switch to enable full 
debug logging.11:57:09 [ERROR] 
11:57:09 [ERROR] For more information about the errors and possible solutions, 
please read the following articles:11:57:09 [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException11:57:09 
Build step 'Invoke top-level Maven targets' marked build as failure___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Can't push code to ONAP Gerrit today

[zhao.huabing]

Hi,




I run into this when trying to push code to ONAP Gerrit:




remote: java.io.IOException: RestClientException{statusCode=Optional.of(403), 
errorCollections=[]}

To http://huabingz...@gerrit.onap.org/r/a/msb/apigateway

 ! [remote rejected] HEAD -> refs/for/master (Failed to check whether or not 
issue MSB-19 exists)




(MSB-19 does exist in ONAP jira https://jira.onap.org/browse/MSB-19)




Some of my colleagues have the same  problems. 


Is it an issue of ONAP Gerrit or something is not correct when I push the 
commit?




Does anyone have any idea?




Thanks for your help.




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

Re: [onap-discuss] [Update] ONAP workflow design and executiondiscussion

[zhao.huabing]

Hi,




Meeting recording has been uploaded to this 
page:https://wiki.onap.org/display/DW/SDC+2017-8-11+ONAP+workflow+design+and+execution+discussion
 




@Michael, If you don't mind, I put the recording under the SDC weekly meeting 
page because workflow designer is part of SDC.




Thanks,

Huabing









Original Mail



Sender:  
To:    

Date: 2017/08/09 21:13
Subject: [onap-discuss] [Update] ONAP workflow design and executiondiscussion






This meeting is rescheduled to Thursday due to conflicts. Sorry for the late 
notification and inconvenience caused.

Hi there,

Huabing is inviting you to a scheduled Zoom meeting.

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/66

Or iPhone one-tap (US Toll):  +14086380968,,66# or 
+16465588656,,66#

Or Telephone:
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
Meeting ID: 699 996 
International numbers available: 
https://zoom.us/zoomconference?m=_5QAuX9O-wb43xJqoNQjTlyYurEIrnWK



ONAP workflow design and execution discussion
This meeting is rescheduled to Thursday due to conflicts. Sorry for the late 
notification and inconvenience caused.Hi there,

Huabing is inviting you to a scheduled Zoom meeting.

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/66

Or iPhone one-tap (US Toll):  +14086380968,,66# or 
+16465588656,,66#

Or Telephone:
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
Meeting ID: 699 996 
International numbers available: 
https://zoom.us/zoomconference?m=_5QAuX9O-wb43xJqoNQjTlyYurEIrnWK














When
Thu 2017-08-10 9pm – 10pm China Time - BeijingWhere
https://zoom.us/j/66 (map)Who
•
Huabing Zhao - creator

•
onap-discuss@lists.onap.org

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

Re: [onap-discuss] [MSB] [AAF] [CLI] Functionality requirement for AAFplugin

[zhao.huabing]

Hi Subhash,





The process would be like:


OOM deploy MSB as the first component 



OOM deploy Registrator, which watches the kubernetes POD events


OOM deploy other ONAP components,including AAF, AAI, Poliy, SO,VFC, APPC, etc.


Registrator get notified with the POD event, then get the service information 
form POD environment variables and service instance(POD) IP from kubernetes


Registrator registers the service endpoints of AAF (and other components) info 
to MSB


MSB use these service info to route service requests






I haven't found AAF docker at https://nexus3.onap.org yet. Hope it will be 
avialable soon.






Thanks,


Huabing



Original Mail



Sender:  
To:  
Date: 2017/08/07 22:19
Subject: [onap-discuss] [MSB] [AAF] [CLI] Functionality requirement for 
AAFplugin







Hello MSB and AAF Team,


 


As per the CLI project requirement, we would like to implement the user 
authentication  using AAF before interacting to services.


From CLI, as a common framework, first step, CLI would discover the required 
service from MSB.


And we would like to install MSB and AAF and make AAF get registered into MSB, 
so that CLI could discover it.


 


So kindly help us on following aspects:


1.  How to install AAF dockers (for the MSB we are following 
https://wiki.onap.org/display/DW/MSB+Test+Environment+Setup)


2.  How to configure AAF with MSB


 


--


Regards,


Subhash Kumar Singh


 


***
 
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**
 
 
***
 This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whoseaddress is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure,reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, pleasenotify the sender by phone or email immediately and 
delete it!
 
***___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Sdc weekly

[zhao.huabing]

Hi Michael,




It seems that the Monday call is too late for Asia and the Tuesday call is too 
early for U.S, May I suggest we combine the two meeting into one at a more 
convient time slot for all the SDC developers?




BR,

Huabing









Original Mail



Sender:  
To:  
Date: 2017/08/08 15:46
Subject: [onap-discuss] Sdc weekly





Hi,
I applolegize for not beeing able to attend todays weekly meeting.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [integration][so] vCPE use workflow design for SO

[zhao.huabing]

Hi,




It seems that this discussion mainly focus on vCPE. We will schedule a seperate 
meeting to generally discuss the workflow design and execution, which is 
relevant to SDC, SO and VF-C.





Thanks,

Huabing










Original Mail



Sender:  
To: lvbo10185543 
CC:     

Date: 2017/08/07 22:41
Subject: Re: [onap-discuss] [integration][so] vCPE use workflow design for SO







+Zahi,David,Eden


 


 


BR,


 


Michael Lando


Opensource & Frontend Team Lead, SDC


AT Network Application Development · NetCom  


Tel Aviv | Tampa | Atlanta | New Jersey |Chicago


···


Office: +972 (3) 5451487


Mobile: +972 (54) 7833603


e-mail: ml6...@intl.att.com


 


 


From: lv.bo...@zte.com.cn [mailto:lv.bo...@zte.com.cn] 
 Sent: Monday, August 07, 2017 12:34 PM
 To: kang...@huawei.com
 Cc: onap-discuss@lists.onap.org dewa...@cloudify.co BULLARD, GIL 
 KLUGER, YOAV  FREEMAN, BRIAN D 
 Lando,Michael 
 Subject: 答复: [onap-discuss] [integration][so] vCPE use workflow design for SO


 


Hi All, 


This is Lv bo from ZTE. According to previous discussion within SDC team, ZTE 
will contribute workflow designer to ONAP and integrate workflow designer to 
SDC. So I'd like to join this meeting. I can present the  demo of workflow 
designer and discuss how to leverage it for vCPE workflow design.


 


The scheduled meeting time 2017-08-08 02:00:00(UTC+08:00) will be too tough for 
Asian developers. So could we reschedule the meeting time to 2017-08-08 
20:00:00(UTC+08:00) ~ 2017-08-08  21:00:00(UTC+08:00). Thanks.

 

Regards.

 

Lv Bo  

 



原始邮件



发件人： 



收件人：     
 



日 期 ：2017年08月05日 02:49



主 题 ：[onap-discuss] [integration][so] vCPE use workflow design for SO




 


Rescheduling to avoid conflict.


 


All,


 


We will discuss details of workflow design for vCPE. DeWayne from SO will join 
the meeting.


 


Thanks,


Kang







[integration][so] vCPE use workflow design for SO




主题：




[integration][so] vCPE use workflow design for SO





时间：




2017-08-08 01:00:00(UTC+08:00) ~ 2017-08-08 02:00:00(UTC+08:00)





地点：




https://zoom.us/j/44





与会人：




onap-discuss@lists.onap.org,dewa...@cloudify.co,gil.bull...@att.com,yoav.klu...@amdocs.com,bf1...@att.com,daniel.silverth...@amdocs.com,ag1...@att.com,ram...@vmware.com,jaco.fou...@ericsson.com,





说明：




Rescheduling to avoid conflict.
 
 All,
 
 We will discuss details of workflow design for vCPE. DeWayne from SO will join 
the meeting.
 
 Thanks,
 Kang
 
 





特此通知！



组织者：kang...@huawei.com


创建时间：2017-08-05 02:47:02(UTC+08:00)







[integration][so] vCPE use workflow design for SO




SUMMARY:




[integration][so] vCPE use workflow design for SO





TIME:




2017-08-08 01:00:00(UTC+08:00) ~ 2017-08-08 02:00:00(UTC+08:00)





LOCATION:




https://zoom.us/j/44





ATTENDEES:




onap-discuss@lists.onap.org,dewa...@cloudify.co,gil.bull...@att.com,yoav.klu...@amdocs.com,bf1...@att.com,daniel.silverth...@amdocs.com,ag1...@att.com,ram...@vmware.com,jaco.fou...@ericsson.com,





DESCRIPTION:




Rescheduling to avoid conflict.
 
 All,
 
 We will discuss details of workflow design for vCPE. DeWayne from SO will join 
the meeting.
 
 Thanks,
 Kang
 
 





Notice is hereby notified!



ORGANIZER:kang...@huawei.com


CREATEDTIME:2017-08-05 02:47:02(UTC+08:00)___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [aai] API Integration with MSB

[zhao.huabing]

Original Mail



Sender:  
To:  
CC:  
Date: 2017/08/01 23:31
Subject: Re: [onap-discuss] [aai] API Integration with MSB







Agreed, and if I read this thread right, the SSL only goes to the gateway - 
after that, the traffic between the gateway and all services is unencrypted 
(Huabing, did I understand that right?).  Not sure how viable this would be 
within a carrier.




Huabing: Yes and no, the traffic between the gateway and all services can be 
encrypted with SSL as well, but it need the support of the services.


Cheers.




On 31 July 2017 at 10:34, SPATSCHECK, OLIVER  (OLIVER) 
 wrote:

 
 > On Jul 31, 2017, at 10:15 AM  EDT, zhaohuab...@gmail.com wrote:
 >
 > Currently, only one-way SSL is supported.
 >
 
 As this is probably the best we can do for R1 we should track this as a 
shortcoming. Even internally one-way SSL is generally not considered to be 
carrier grade security.
 
 Oliver___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Versioning for Amsterdam

[zhao.huabing]

Hi Gildas,






I suggest we align the versioning mechanism of the deliverable with REST API 
version.






I didn't go to the versioning discussion during the virtual developer meeting. 
But from what I learned by this mail, I think there is no conflict between what 
you folks are suggesting and the REST API versioning mechanism 
https://wiki.onap.org/display/DW/RESTful+API+Design+Specification+for+ONAP#RESTfulAPIDesignSpecificationforONAP-Versioning







What do you think?






BR,


Huabing



Original Mail



Sender:  
To:  
CC:  
Date: 2017/07/27 22:36
Subject: Re: [onap-discuss] Versioning for Amsterdam






Hi Gildas, 
 
What process to you recommend so that we can settle on this? Do we need to go 
through TSC?
 
On Jul 21, 2017, at 6:22 PM, Gildas Lanilis  wrote:
 


I see Olivier is leading a session on versioning, excellent I will attend. I 
won't have time to cover this during Release Planning.
 
Looks like there is a trend toward option 2 (multiple version of jars files 
embedded within 1 docker image) with some good reasons. Thinking loud, as all 
projects will be a Docker image, when we will release these Docker images in  
November, I will be incline to mark these Docker images as version 1.0.0. for 
Amsterdam and later 2.0.0 for Beijing (and of course with semantic versioning 
if we need in the middle to deliver patches).
 
So we will end up with Something like:
 
Amsterdam Release:1.0.0
 
AAI Docker Image: 1.0.0

 AAI cpt 1: 2.0.3

 AAI cpt2: 1.4.2

 AAI cpt3: 0.0.9

 Other stuff: 1.2.6
 
AAFDocker Image: 1.0.0

 AAI cpt 1: 2.0.3

 AAI cpt2: 2.4.2

 AAI cpt3: 1.0.9

Other stuff: 1.2.7
 
Beijing: 2.0.0
 
AAI Docker Image: 2.0.0

 AAI cpt1: 2.5.3

 AAI cpt2: 2.4.2

 AAI cpt3: 1.0.9

 Other stuff: 1.2.8
 
AAF Docker Image: 2.0.0

 AAF cpt1: 2.9.3

 AAF cpt2: 3.5.2

 AAF cpt3: 1.0.9

Other stuff: 2.2.6
  
Let me know if that resonate to you or if I should stop and go in weekend J
 
Thanks,

Gildas

ONAP Release Manager

1 415 238 6287
  
-Original Message- From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Andrew Grimberg Sent: 
Thursday, July 20, 2017 11:00 AM To: Gary Wu  Cc: 
onap-discuss@lists.onap.org Subject: Re: [onap-discuss] Versioning for Amsterdam
 
It's the same process we would follow for a single simultaneous release.

The difference is that each component would be (and presently ONAP does

this) producing their own staging repository.
 
So, the release is then a matter of identifying which repositories are part of 
the release and doing the artifact signing on those and releases in nexus to 
the release repository.
 
The Simultaneous Release would be more of an identifying what components are 
actually part of the tested SR and potentially some final single produced 
downloadable object that doesn't do the build, but just incorporates the 
individually  released components.
 
LF Release Engineering (RelEng) has been fixing up our release scripts dealing 
with this sort of thing. They are now part of the lftools python project [0] 
[1] (installable via PyPi). ODL itself has started down the road of individual  
components being able to release off sync from each other with the current 
Nitrogen release cycle. The odlparent project has already had at least 3 
different releases in the middle of the cycle! We expect that the next project 
up the stack (yangtools) will  do that with the Oxygen release as they 
transition to SemVer which really is a requirement for this to work correctly.
 
We have additional work coming that will allow us to automate the artifact 
signing and will therefore allow us to move more of the release processes into 
the hands of the community itself instead of relying on RelEng for so much  of 
it.
 
-Andy-
 
[0] https://gerrit.linuxfoundation.org/infra/#/admin/projects/releng/lftools

[1] https://github.com/lfit/releng-lftools
 
On 07/20/2017 10:41 AM, Gary Wu wrote:

> Hi Andy,

> 

> Can you chime in on how the release process would work (vis-à-vis use of 
> staging repos, artifact signings, etc.) if ONAP  decides to have independent 
> version numbers and possibly independent release cycles for each module?

> 

> Thanks,

> Gary

> 

> 

> -Original Message-

> From: onap-discuss-boun...@lists.onap.org

> [mailto:onap-discuss-boun...@lists.onap.org]  On Behalf Of Gino Fraboni

> Sent: Thursday, July 20, 2017 7:04 AM

> To: SPATSCHECK, OLIVER (OLIVER)   Yunxia

> Chen 

> Cc: onap-discuss@lists.onap.org

> Subject: Re: [onap-discuss] Versioning for Amsterdam

> 

> 

> I'll throw in my +1 for version 2 as well.

> And semantic versioning makes complete sense to me.

> 

> 

> Gino Fraboni

> 

Re: [onap-discuss] [all] [integration] [bootstrap] vagrant-onapprojectavailable into Integration repo

[zhao.huabing]

Thanks, Helen.







Original Mail



Sender:  
To: zhaohuabing10201488 
CC:  
Date: 2017/07/28 10:20
Subject: Re: [onap-discuss] [all] [integration] [bootstrap] 
vagrant-onapprojectavailable into Integration repo







Hi, Huabing,


Yes, at this moment, the tools that Victor and his team are developing are used 
for Developer to start their development and testing environment fast. It is 
part of Integration project.   


 


Regards,


 



Helen Chen


 



From:  on behalf of 
"zhao.huab...@zte.com.cn" 
 Date: Thursday, July 27, 2017 at 6:02 PM
 To: "victor.mora...@intel.com" 
 Cc: "onap-discuss@lists.onap.org" 
 Subject: Re: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap 
projectavailable into Integration repo



 


Hi Victor,

 

Thanks for bring this useful tool to ONAPer !

 

I'd like to understand the relationship between this project and OOM.

It seems that this project just intend to provide a handy development 
environment for ONAP developer and will not be part of OOM, which aim to the 
production deployment. Do I understand correctly?

 

Thanks,

Huabing

 


Original Mail



Sender:  



To:  



Date: 2017/07/27 06:57



Subject: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap 
projectavailable into Integration repo




 


ONAPers,


 


The vagrant-onap project started as an alternative to deploy ONAP services in 
Virtual Machines hosted locally without the need of an OpenStack deployment.   
After several changes and additions to this project,  its goal has changed to 
provision a Development Environment.  Its current implementation support 
different providers (like VirtualBox, Libvirt and OpenStack) and has been 
tested in some OS(like Ubuntu,  Mac OS).  This is an ongoing effort to collect 
instructions  and standardize the methods to build and compile ONAP artifacts, 
as you can expect there are many things that are still missed so I encourage to 
everyone to take a look of the scripts placed into  lib folder[1] and improve 
the documentation[2][3]. We have plans  to add more Unit Tests to this 
project[4] to validate any change.


 


Thanks


Victor Morales


irc: electrocucaracha


 


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


[2] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/README.md


[3] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/doc/source


[4] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/tests___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap projectavailable into Integration repo

[zhao.huabing]

Hi Victor,




Thanks for bring this useful tool to ONAPer !




I'd like to understand the relationship between this project and OOM.

It seems that this project just intend to provide a handy development 
environment for ONAP developer and will not be part of OOM, which aim to the 
production deployment. Do I understand correctly?




Thanks,

Huabing






Original Mail



Sender:  
To:  
Date: 2017/07/27 06:57
Subject: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap 
projectavailable into Integration repo







ONAPers,


 


The vagrant-onap project started as an alternative to deploy ONAP services in 
Virtual Machines hosted locally without the need of an OpenStack deployment.  
After several changes and additions to this project,  its goal has changed to 
provision a Development Environment.  Its current implementation support 
different providers (like VirtualBox, Libvirt and OpenStack) and has been 
tested in some OS(like Ubuntu, Mac OS).  This is an ongoing effort to collect 
instructions  and standardize the methods to build and compile ONAP artifacts, 
as you can expect there are many things that are still missed so I encourage to 
everyone to take a look of the scripts placed into lib folder[1] and improve 
the documentation[2][3]. We have plans  to add more Unit Tests to this 
project[4] to validate any change.


 


Thanks


Victor Morales


irc: electrocucaracha


 


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


[2] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/README.md


[3] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/doc/source


[4] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/tests___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [PTLs][MSB] Need your action: Fill In ONAP Microservices Information for MSB Integration with your project

[zhao.huabing]

Dear PTLs,

 

ONAP services need to be registered to MSB to leverage the service 
discovery/routing/LB capabilities of MSB. I created a wiki page to collect all 
the service end points information of ONAP.

 https://wiki.onap.org/display/DW/ONAP+Services+List 




Could you please review them and fill in the table of your project? If you have 
any questions, please let me know, I can organize a meeting for MSB demo and 
introduce the MSB Integration procedure. It's easy and has no invasion to the 
existing codes of each project.


 

Thanks,

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

Re: [onap-discuss] API Format

[zhao.huabing]

Hi Varun,

So far Swagger is recommended for API documentation.

https://wiki.onap.org/display/DW/RESTful+API+Design+Specification+for+ONAP 




BR,

Huabing






Original Mail



Sender:  
To:  
Date: 2017/07/27 06:02
Subject: [onap-discuss] API Format







Hi all,


Since we have to document APIs for M2 Release Functionality Freeze Milestone, 
is there any defined format for the APIs. Is Swagger format fine?


 


Thanks


Varun Gudisena


Sr. Software Engineer


AT Services, Inc.


 


211 S Akard St,


Dallas ,TX 75202


USA


Ph: 617-834-4157___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [MSB][OOM]The July Virtual Developers Event Topic : OOM & MSB Interaction

[zhao.huabing]

Hi David,




Given the current situation, MSB should take the service endpoint registration 
integration with kubernetes implementation as its priority for Amsterdam and 
integration with cloudify implementation as a stretch goal.




As we discussed in the last OOM meeting, we need a repo to accommodate the 
registrator codes for kubernetes service. Can you help to create that repo?  
Please let me know if you have any concerns or question.





Release Components Name

Components Name

Components Repository name

Maven Group ID

Components Description
registratoroom/registratororg.onap.oom.registratorRegister the service 
endpoints to MSB so it can be used for service request routing and load 
balancing. Registrator puts service endpoints info to MSB discovery 
module(Consul as the backend) when an ONAP component is deployed by OOM, and 
update its state along with the life cycle, such as start, stop, scaling, etc.


Resources committed to the Release


Thanks,

Huabing






Original Mail



Sender:  
To:  
CC: zhaohuabing10201488   
   
MengZhaoXing10024238  
 
Date: 2017/07/26 19:39
Subject: Re: [MSB][OOM]The July Virtual Developers Event Topic :  OOM & MSB 
Interaction






Hi John
 
Let’s recap what was discussed and agreed as a team:

* For Amsterdam release, Kubernetes is the first OOM technical implementation 
to be created. This is the seed code available and what the team agreed to work 
on

* The cloudily implementation has not been demoed yet and no seed code 
available. It was agreed by the team that cloudily would be a stretch target.
 
I want to make sure we align to what the OOM team has agreed to deliver.
 
Comments?
 
On Jul 25, 2017, at 6:39 PM, NG, JOHN  wrote:
 


Huabing,

Ok, let’s focus on Consul integration for the Amsterdam release …

-  In  Day 0 OOM instantiation, Cloudify is the first OOM module to be 
created.


-  Cloudify  creates Consul as the next OOM module.   Cloudify 
registers itself in Consul.


-  Cloudify  then creates the rest of the OOM modules (Postgres, API 
Handler, Dashboard), and registers each module in Consul.  And Consul starts 
performing health checks against them.


-  OOM  instantiation is now complete.


-  OOM  deploys MSB as one of the first ONAP components.  OOM 
provides/configures MSB with the location of the Consul API for access and 
discovery.


-  OOM  then continues to deploy the rest of the ONAP components and 
modules, and registers them with Consul.


Comments?
 
John
 
--- John Ng AT Labs – D2 
Architecture 200 Laurel Ave, D5-3D16 Middletown, NJ 07748 +1 732 420 3742 +1 
732 310 3253 (mobile) joh...@att.com 
---
 
From: zhao.huab...@zte.com.cn  [mailto:zhao.huab...@zte.com.cn]  Sent: Monday, 
July 24, 2017 9:48 PM To: NG, JOHN  Cc: LUCAS, JACK 
 HU, JUN NICOLAS  BENNETT, RICH 
 david.sauvag...@bell.ca TORAB, HABIB M  
roger.maitl...@amdocs.com MURRAY, JOHN  
meng.zhaoxi...@zte.com.cn RATH, CHRISTOPHER A  GAULD, 
ANDREW G  onap-discuss@lists.onap.org Subject: Re:RE: 
[MSB][OOM]The July Virtual Developers Event Topic :  OOM & MSB Interaction
 

Hi John,


 


I'm afraid that I can't agree that.


 


There is a clear boundary between OOM and MSB and their project scopes are 
totally different. I think these have already been fully discussed in the 
community in the last few months and approved by TSC at the Beijing meeting.


 


Right now our first priority should be the release goal of Amsterdam and we 
should focus on our last agreement - the integration point at Consul. Given 
that MSB is providing Microservice Infrastructure for ONAP components, I hope 
we can do it ASAP.


 


Thanks,


Huabing


 


 




Original Mail





Sender:  



To: zhaohuabing10201488    
    
  MengZhaoXing10024238 
  



CC:  



Date: 2017/07/25 07:05



Subject: RE: [MSB][OOM]The July Virtual Developers Event Topic :  OOM & MSB 
Interaction



 




Hi Huabing,

I am not sure whether this topic has been discussed yet.  We have an 
alternative proposal and added Slide 6 on the ppt file you uploaded on the MSB 
page.  Please   review and share your thoughts. 
 
Our proposal is to merge MSB and OOM.  We agree that there should be a common 
software framework and implementation of 

Re: [onap-discuss] [SDC] Volte csar packages //Re: CSAR from SDC

[zhao.huabing]

Hi Zahi, 




I see that you're in the "Interested in attending" list of "SDC Questions (Day 
3- Main Conf. Bridge)". So I guess you will be participating this meeting this 
afternoon?




If it's possible, could we discuss the support of VoLTE TOSCA model and other 
issues such as the TOSCA substitution mapping?




We're trying to import the TOSCA VNF Node type and design the VoLTE service in 
SDC. However, because the TOSCA based VNF can't be imported into SDC(only heat 
supported right now), it's hard for us to tell how many gaps we have to support 
the VoLTE use case. So it would be very helpful if you could have time to 
review the VoLTE csar packages in advance and point out some gaps in the 
meeting.




Thanks,

Huabing



Original Mail



Sender:  
To: zhaohuabing10201488  
CC:  YuanHu10090474
Date: 2017/07/24 23:14
Subject: Re: [SDC] Volte csar packages //Re: [onap-discuss] CSAR from SDC





We’re looking at the issues and we’ll return with an answer once we have it.

Zahi Kapeluto
Lead Architect, Network Communications LOB
AT Network Applications Development · SD
Tel Aviv | Tampa | Atlanta | New Jersey | Chicago
·
Mobile: +972 (54) 6636831
Office: +972 (3) 9280064

From: "zhao.huab...@zte.com.cn" 
Date: Monday, 24 July 2017 at 7:47
To: ZAHI KAPELUTO , "Rozin, Eden" , 
"Lando,Michael" 
Cc: "onap-discuss@lists.onap.org" , 
"yuan@zte.com.cn" 
Subject: [SDC] Volte csar packages //Re: [onap-discuss] CSAR from SDC


Hi ,



I created a jira issue to track the substitution issue.



Besides, attached are the VoLTE csar packages which have been used for OPEN-O 
Mercury Release.

Please review it, if there are anything SDC can't support now, we may need to 
add jira issues to track them.



Huabing








Original Mail
Sender: zhaohuabing10201488
To:  
CC:  YuanHu10090474 
Date: 2017/07/21 12:32
Subject: Re: [onap-discuss] CSAR from SDC



Hi Zahi,



I understand what's substitution mapping for, if you take a loot at the TOSCA 
spec, it says:

substitution_mappings


no


N/A


An optional declaration that exports the topology template as an implementation 
of a Node type.



This also includes the mappings between the external Node Types named 
capabilities and requirements to existing implementations of those capabilities 
and requirements on Node templates declared within the topology template.


I don't see the red part " the mappings between the external Node Types named 
capabilities and requirements to existing implementations of those capabilities 
and requirements on Node templates declared within the topology template" in 
the SDC service template. That's where my question comes from.



I took the example from official TOSCA spec here:  
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.1/csprd02/TOSCA-Simple-Profile-YAML-v1.1-csprd02.html#_Toc474149740

2.11.3Defining the details of a subsystem

Example 19 - Implementation of a TransactionSubsytem node type using 
substitution mappings



BR,

Huabing










Sender:  
To: zhaohuabing10201488
CC:   YuanHu10090474 

Date: 2017/07/20 21:51
Subject: Re: [onap-discuss] CSAR from SDC


Hi Zhao,

Substitution Mapping is used for embedding a complete Topology Template into 
another, higher-level, Topology Template as a Node Template as seen in the 
image below:

[cid:image001.png@01D30178.669A2E00]

Your sample TOSCA below seems wrong, where did you take it from?
Here is an example of substitution mapping:

topology_template:
  node_templates:
ExtVL 0:
  type: org.openecomp.resource.vl.extVL
  metadata:
invariantUUID: df44a9d0-024a-48fc-bd0a-12aaf69dd89e
UUID: 6bacc8ad-f5ca-4774-b5f6-bab441b3eba8
customizationUUID: cdc9e73c-245c-4569-ae34-2156acefdc2c
version: '5.0'
name: ExtVL
description: ECOMP generic virtual link (network) base type for all 
other service-level and global networks
type: VL
category: Generic
subcategory: Network Elements
resourceVendor: ATT (Tosca)
resourceVendorRelease: 1.0.0.wd03
resourceVendorModelNumber: ''
  properties:
network_assignments:
  is_external_network: false
  

Re: [onap-discuss] [MSB][OOM]The July Virtual Developers Event Topic : OOM & MSB Interaction

[zhao.huabing]

Hi John,




I'm afraid that I can't agree that.




There is a clear boundary between OOM and MSB and their project scopes are 
totally different. I think these have already been fully discussed in the 
community in the last few months and approved by TSC at the Beijing meeting.




Right now our first priority should be the release goal of Amsterdam and we 
should focus on our last agreement - the integration point at Consul. Given 
that MSB is providing Microservice Infrastructure for ONAP components, I hope 
we can do it ASAP.




Thanks,

Huabing













Original Mail



Sender:  
To: zhaohuabing10201488   
   
 MengZhaoXing10024238 
 
CC:  
Date: 2017/07/25 07:05
Subject: RE: [MSB][OOM]The July Virtual Developers Event Topic :  OOM & MSB 
Interaction







Hi Huabing,


I am not sure whether this topic has been discussed yet.  We have an 
alternative proposal and added Slide 6 on the ppt file you uploaded on the MSB 
page.  Please  review and share your thoughts. 


 


Our proposal is to merge MSB and OOM.  We agree that there should be a common 
software framework and implementation of the service registration and service 
discovery  functions.  We agree that there should be a shared Consul instance 
to support the registration/discovery functions.  We want to avoid any 
potential collisions where multiple parties register services with the same 
names/URIs – so we might need to work out  rules (name spaces) to prevent them. 


 


One question we have is whether there is a use case that shows MSB operating 
outside of OOM for microservices/service endpoints?  We could not think of any 
and  so recommend that merging MSB and OOM be considered.  We see that 
microservices and ONAP components being deployed and managed by OOM in a common 
process:


1.   OOM (Cloudify) creates virtualized infrastructure and 
container/kubernetes cluster via TOSCA based blueprints


2.   OOM (Cloudify) triggers (via kubernetes) the dockerized image 
(microservice or ONAP component module) to be created


3.   OOM (Registry) listens for container creation in the pod and registers 
the new container


4.   OOM (Discovery) updates inventory database and begins to health check 
the new container (microservice or ONAP module)


5.   OOM (Discovery) updates health status to Internal/External Gateways


6.   OOM (Gateways) route service requests to healthy service endpoints


7.   OOM (Cloudify) performs recovery, healing, scale actions based on 
health status


 


Please provide feedback and we would be happy to discuss.


 


John


---
John Ng
AT Labs – D2 Architecture
200 Laurel Ave, D5-3D16
Middletown, NJ 07748
+1 732 420 3742
+1 732 310 3253 (mobile)
 joh...@att.com
---


 


From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn] 
 Sent: Friday, July 21, 2017 2:33 AM
 To: LUCAS, JACK  HU, JUN NICOLAS  
BENNETT, RICH  david.sauvag...@bell.ca TORAB, HABIB M 
 roger.maitl...@amdocs.com MURRAY, JOHN  
NG, JOHN   meng.zhaoxi...@zte.com.cn zhao.huab...@zte.com.cn
 Cc: onap-discuss@lists.onap.org
 Subject: [MSB][OOM]The July Virtual Developers Event Topic :  OOM & MSB 
Interaction


 

Hi there,

 

Will you be able to attend this topic:  OOM & MSB Interaction? I would 
appreciate it if both OOM team and the AT cloudify proposal folks could join 
to discuss it.

https://wiki.onap.org/pages/viewpage.action?pageId=8232264 

 

Thanks,

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

Re: [onap-discuss] 答复: Re: About workflow engine

[zhao.huabing]

Hi Zohar,




We have discussed within SDC team about the design time workflow tool, I can 
show the workflow designer demo in this meeting if you folks are interested.




Thanks,

Huabing







Original Mail



Sender:  
To: ZhangMaoPeng10030173 
CC:  
Date: 2017/07/24 18:58
Subject: Re: [onap-discuss]答复: Re:  About workflow engine 







Hi All


 


We need to have the first meeting this week, let's start with a hour.


I’ve created a doodle scheduling assistant here 
https://doodle.com/poll/zsg9i959suy7f3d7 please mark the slots of your 
convenience today.


 


NOTE all times where set at UTC+3 time zone (not sure id doodle is timezone 
aware)


 


Today EOD I’ll set a meeting to the time convenient to most people


 


Thank you all Z


 


 


From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Sent: Friday, July 21, 2017 10:01 AM
 To: zk0...@intl.att.com
 Cc: seshu.kuma...@huawei.com onap-discuss@lists.onap.org Zohar Sacks 

 Subject: 答复: Re: 答复: Re: [onap-discuss] About workflow engine 


 

Hi Zahi

 

   The meeting time may conflict with the virtual development meeting. 

   IMHO, I think both the design-time and runtime are important.

   We can talk the requirement from the design-time, and also want to discuss 
the possiblity that make the workflow engine  as mirco service and make the 
designer more easy。

 

Best Regards

Maopeng


原始邮件



发件人： 



收件人：张茂鹏10030173



抄送人：    




日 期 ：2017年07月20日 20:59



主 题 ：Re: 答复: Re: [onap-discuss] About workflow engine 




 


I would like to focus our discussion on design-time change management workflows 
(e.g., pause, upgrade etc.) and how current tooling fits into the overall SDC 
architecture and UX.
 
 Can I set a meeting for next Tuesday, 17:00 UTC+3?
 
 Zahi Kapeluto
 Lead Architect, Network Communications LOB
 AT Network Applications Development · SD
 Tel Aviv | Tampa | Atlanta | New Jersey | Chicago
 ·
 Mobile: +972 (54) 6636831
 Office: +972 (3) 9280064
 
 From: "zhang.maope...@zte.com.cn" 
 Date: Thursday, 20 July 2017 at 4:54
 To: ZAHI KAPELUTO 
 Cc: "seshu.kuma...@huawei.com" , 
"onap-discuss@lists.onap.org" , "SACKS, ZOHAR" 

 Subject: 答复: Re: [onap-discuss] About workflow engine
 
 
 Hi Zahi
 
 
 
 Yes, definite.  Workflow engines have different workflow templates. If 
the workflow is designed by user via SDC,  it will effect SDC.
 
 In my mind, some workflow is used by user, maybe some workflow is used 
only by the code developer as well, such as Camunda offline tools, DG offline 
tools,
 
 However  if the workflow design for user can be integrated with SDC 
via portal SDK, It will be greater.
 
 
 
 Best Regards
 
 Maopeng
 原始邮件
 发件人： 
 收件人：张茂鹏10030173  
 抄送人： 
 日 期 ：2017年07月20日 02:27
 主 题 ：Re: [onap-discuss] About workflow engine
 
 
 Can we also have a discussion about the workflow designer (which should be 
part of SDC), its capabilities, proposed architecture etc.?
 
 Zahi Kapeluto
 Lead Architect, Network Communications LOB
 AT Network Applications Development · SD
 Tel Aviv | Tampa | Atlanta | New Jersey | Chicago
 ·
 Mobile: +972 (54) 6636831
 Office: +972 (3) 9280064
 
 From:  on behalf of 
"zhang.maope...@zte.com.cn" 
 Date: Wednesday, 19 July 2017 at 12:46
 To: "seshu.kuma...@huawei.com" , 
"onap-discuss@lists.onap.org" 
 Subject: [onap-discuss] About workflow engine
 
 
 Hi seshu and guys
 
 
 
About the workflow engine(WFE) usage, I have an idea and want to share in 
the community, If I am wrong, please correct me.
 
In the SO or controllers projects of ONAP,  there are many opensource party 
workflow engines, such as Camunda, MSO, DG, aria tosca workflow engine, ...etc.
 
Most of those workflow engines now bind to the project.
 
Workflow engines self are independant fucntion and can be decoupled with 
the specific project logic functions.
 
Could the projects make them as micro service? If some projects use the 
same one,  the WFE instance could be shared among them.
 
If possible, we can create an group or wiki page to discuss the issue.
 
Thanks all.
 
 
 
 Best Regards
 
 Maopeng
 
 
 
 
 
 
 
 
 
 
 
 
 


 





 



This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,you may review at 

Re: [onap-discuss] [oom][msb][cli] ONAP component health status

[zhao.huabing]

Hi Kanagaraj,




Yes, you are correct. OOM will be responsible for the health status of each 
service and will also update into MSB.




BR,

Huabing



Original Mail



Sender:  
To:  
CC:  
Date: 2017/07/24 23:57
Subject: [onap-discuss] [oom][msb][cli] ONAP component health status







Dear OOM & MSB team,


 


From CLI, we are planning to provide the commands to report health status for 
each ONAP component, which currently provides a specific REST API for querying 
their health status.


Based on my understanding , in release A, I think that OOM will register all 
micro-services into MSB and from where, all other services/users will discover 
the details of a given micro-service.


As part of it, I have following question:


 


Will OOM update health status of each service will also updated into MSB?  
Thanks.


 


Regards


Kanagaraj M


***
 
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**
 
***
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
***___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Registrator Repo //Re: Invitation: [oom] Weekly Meeing @ Weekly from 7am to 8am onWednesday (PDT) (david.sauvag...@bell.ca)

[zhao.huabing]

Hi David,




As we discussed at the last meeting, OOM needs another repo to accommodate the 
registrator codes, can you help ask the TSC to approve this repo?

The repo info has been added to the  Resources and Repositorie wiki page.




Release Components Name




Components Name

Components Repository name

Maven Group ID

Components Description
registratoroom/registratororg.onap.oom.registratorRegister the service 
endpoints to MSB so it can be used for service request routing and load 
balancing. Registrator puts service endpoints info to MSB discovery 
module(Consul as the backend) when an ONAP component is deployed by OOM, and 
update its state along with the life cycle, such as start, stop, scaling, etc.






Thanks,


Huabing






Original Mail



Sender:  
To:  
CC: zhaohuabing10201488 
Date: 2017/07/19 05:30
Subject: Re: Invitation: [oom] Weekly Meeing @ Weekly from 7am to 8am 
onWednesday (PDT) (david.sauvag...@bell.ca)







Agenda for tomorrow:


· Status update


oCloudify for OOM: set timing for demo and seed code review


oOOM - MSB Integration: followup from the email from Huabing


oPlatform configuration management: A proposed approach by AMDOCS


· Getting momentum: Next steps for kicking-off implementation


Thanks,


 



From: linuxfoundation.org_1rmtb5tpr3uc8f76fmflplo...@group.calendar.google.com
 When: 10:00 AM - 11:00 AM July 19, 2017 
 Subject: Invitation: [oom] Weekly Meeing @ Weekly from 7am to 8am on Wednesday 
(PDT) (david.sauvag...@bell.ca)
 Location: https://zoom.us/j/118908904



 


 


more  details »


[oom] Weekly Meeing
 


Hi there,

ONAP Meeting 5 is inviting you to a scheduled Zoom meeting.


 

Join from PC, Mac, Linux, iOS or Android: 

https://zoom.us/j/118908904


 

Or iPhone one-tap (US Toll): +14086380968,,118908904# or 
+16465588656,,118908904#


 

Or Telephone:
 
 

Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
 
 

+1 855 880 1246 (US Toll Free)
 
 

+1 877 369 0926 (US Toll Free)
 
 

Meeting ID: 118 908 904
 
 

International numbers available: 

https://zoom.us/zoomconference?m=RjcDSzvXlwMWG5gaHA7q936bD1fmNWjr


 


 


 


 


 


 


 


 


 


 


 


 



When



Weekly from 7am to 8am on Wednesday Pacific Time


Where



https://zoom.us/j/118908904 (map)


Calendar



david.sauvag...@bell.ca


Who



•



kp...@linuxfoundation.org - creator




•



david.sauvag...@bell.ca 




•



onap-discuss@lists.onap.org 





Going? All events in this series: Yes  - Maybe  - No more options »

Invitation from Google Calendar

You are receiving this courtesy email at the account david.sauvag...@bell.ca 
because you are an attendee of this event.

To stop receiving future updates for this event, decline this event. 
Alternatively you can sign up for a Google account at 
https://www.google.com/calendar/ and control your notification settings  for 
your entire calendar.

Forwarding this invitation could allow any recipient to modify your RSVP 
response. Learn More.___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [MSB][OOM]The July Virtual Developers Event Topic : OOM & MSB Interaction

[zhao.huabing]

Hi there,




Will you be able to attend this topic:  OOM & MSB Interaction? I would 
appreciate it if both OOM team and the AT cloudify proposal folks could join 
to discuss it.

https://wiki.onap.org/pages/viewpage.action?pageId=8232264 




Thanks,

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

Re: [onap-discuss] CSAR from SDC

[zhao.huabing]

Hi Zahi,

Thanks for your answer.




1.  Can't find the corresponding node template for the defined capabilities and 
requirements in the substitution_mappingsThe substation mapping in the below 
example contains capabilities/requirements. Those are the caps/reqs defined by 
this node template so why are you looking for any other node template?




Regarding this question, as I understand it, it's the mappings between the 
external Node Types named capabilities and requirements to existing 
implementations of those capabilities and requirements on Node templates 
declared within the topology template.  

Let me use the below TOSCA service template as an example,

the substitution_mappings capability message_receiver expose the 
message_receiver capability of  app node template, 

the substitution_mappings requirement database_endpoint  expose the database 
capability of  app node template, 

tosca_definitions_version: tosca_simple_yaml_1_0




topology_template:

  description: Template of a database including its hosting stack.

# omitted for brevity

  substitution_mappings:

node_type: example.TransactionSubsystem

capabilities:

  message_receiver: [ app, message_receiver ]

requirements:

  database_endpoint: [ app, database ]

  node_templates:

app:

  type: example.SomeApp

  properties:

# properties omitted for brevity

  capabilities:

message_receiver:

  properties:

service_ip: { get_input: mq_service_ip }

# other properties omitted for brevity

  requirements:

- database:

# details omitted for brevity

- host: websrv




In this service template  service-57431726F7e64a30Ae52-template.yml, I don't 
see this mapping.




Did I miss anything?




Thanks,

Huabing



Original Mail



Sender:  
To:  zhaohuabing10201488
CC:  YuanHu10090474 
Date: 2017/07/18 22:00
Subject: Re: [onap-discuss] CSAR from SDC





Hi Huabing,

Additional answers :

  1.  Can't find the corresponding node template for the defined capabilities 
and requirements in the substitution_mappings
The substation mapping in the below example contains capabilities/requirements. 
Those are the caps/reqs defined by this node template so why are you looking 
for any other node template?

  1.  Does SDC support the definition of TOSCA Group?
Yes

  1.  Does SDC support the definition of TOSCA Policy?
Yes

  1.  Does SDC support the mapping of Input and Node Template property?
Yes

  1.  Does SDC support the mapping of Output and Node Template attribute?
No
Zahi Kapeluto
Lead Architect, Network Communications LOB
AT Network Applications Development · SD
Tel Aviv | Tampa | Atlanta | New Jersey | Chicago
·
Mobile: +972 (54) 6636831
Office: +972 (3) 9280064

From: "SACKS, ZOHAR" 
Date: Tuesday, 18 July 2017 at 16:38
To: "zhao.huab...@zte.com.cn" 
Cc: ZAHI KAPELUTO , "onap-discuss@lists.onap.org" 
, "yuan@zte.com.cn" , 
"Rozin, Eden" 
Subject: RE: [onap-discuss] CSAR from SDC

At current time each import will create new VSP version and deletes (with 
alert) the previous data

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhao.huab...@zte.com.cn
Sent: Tuesday, July 18, 2017 10:34 AM
To: zhao.huab...@zte.com.cn
Cc: zk0...@intl.att.com onap-discuss@lists.onap.org yuan@zte.com.cn 
er4...@intl.att.com
Subject: Re: [onap-discuss] CSAR from SDC


One more question about SDC:

 If I import the same heat package into SDC for multiple times, how does SDC 
handle it? Will SDC create different version of the same VF, or update the 
existing VF, or just take them as different VNs?
Original Mail
Sender: zhaohuabing10201488
To:  >
CC:  > 
> 
>yuanhu10090474
Date: 2017/07/18 11:12
Subject: Re: [onap-discuss] CSAR from SDC



Hi Michael,



Could we discuss these questions at today's meeting?



Thanks,

Huabing






Sender:  >
To: zhaohuabing10201488 > 
>
CC: MengZhaoXing10024238YuanHu10090474
Date: 2017/07/17 18:08
Subject: Re:CSAR from SDC


+Eden,Zahi
Please assit

 Original Message 
From: zhao.huab...@zte.com.cn
Date: Mon, Jul 17, 2017, 12:24
To: "Lando,Michael" >
CC: meng.zhaoxi...@zte.com.cn, 

Re: [onap-discuss] CSAR from SDC

[zhao.huabing]

One more question about SDC:

 If I import the same heat package into SDC for multiple times, how does SDC 
handle it? Will SDC create different version of the same VF, or update the 
existing VF, or just take them as different VNs?



Original Mail



Sender: zhaohuabing10201488
To:  
CC:    
yuanhu10090474
Date: 2017/07/18 11:12
Subject: Re: [onap-discuss] CSAR from SDC







Hi Michael,






Could we discuss these questions at today's meeting?






Thanks,


Huabing















Sender:  
To: zhaohuabing10201488  
CC: MengZhaoXing10024238YuanHu10090474
Date: 2017/07/17 18:08
Subject: Re:CSAR from SDC





+Eden,Zahi
Please assit

 Original Message 
From: zhao.huab...@zte.com.cn
Date: Mon, Jul 17, 2017, 12:24
To: "Lando,Michael" 
CC: meng.zhaoxi...@zte.com.cn, yuan@zte.com.cn
Subject: Re:CSAR from SDC


Hi Michael,


We get a couple of questions here after studying the example.


1. Can't find the corresponding node template for the defined capabilities and 
requirements in the substitution_mappings


For example:

 The substitution_mappings defined in the 
service-57431726F7e64a30Ae52-template.yml of service-vvg.csar


tosca_definitions_version: tosca_simple_yaml_1_0

# omitted here for brevity

topology_template:

  node_templates:

d7c95393-7396-4d74-a3b0 0:

  type: org.openecomp.resource.vf.D7c9539373964d74A3b0

  metadata:

invariantUUID: 7564e792-a8af-4f73-9910-2e3b88dfa862

UUID: 31d208bc-9744-4060-baa8-2decca503193

customizationUUID: 2f9f65ab-6aef-48fc-a63f-5ac96e88c0ad

version: '1.0'

name: d7c95393-7396-4d74-a3b0

description: vendor software product

type: VF

category: Generic

subcategory: Abstract

resourceVendor: 06715d78-893c-4a45-88c1

resourceVendorRelease: '1.0'

# omitted here for brevity

  substitution_mappings:

node_type: org.openecomp.service.57431726F7e64a30Ae52

capabilities:

  d7c9539373964d74a3b00.cinder_volume.feature:

  - cinder_volume

  - cinder_volume.feature

  d7c9539373964d74a3b00.cinder_volume.attachment:

  - cinder_volume

  - cinder_volume.attachment

requirements:

  d7c9539373964d74a3b00.cinder_volume.dependency:

  - cinder_volume

  - cinder_volume.dependency


2. Does SDC support the definition of  TOSCA Group?

3. Does SDC support the definition of TOSCA  Policy?

4. Does SDC support the mapping of Input and Node Template property?

5. Does SDC support the mapping of Output and Node Template attribute?


Thanks,

Huabing







Original Mail
Sender:  
To: zhaohuabing10201488
Date: 2017/07/11 22:36
Subject: CSAR from SDC

Hi,
As discussed today on the call.
I am attaching the scar created for the 3 services part of the uses case 
currently supported.


BR,

Michael Lando
Opensource & Frontend Team Lead, SDC
AT Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
···
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: ml6...@intl.att.com___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] CSAR from SDC

[zhao.huabing]

Hi Michael,






Could we discuss these questions at today's meeting?






Thanks,


Huabing






Original Mail



Sender:  
To: zhaohuabing10201488  
CC: MengZhaoXing10024238YuanHu10090474
Date: 2017/07/17 18:08
Subject: Re:CSAR from SDC





+Eden,Zahi
Please assit

 Original Message 
From: zhao.huab...@zte.com.cn
Date: Mon, Jul 17, 2017, 12:24
To: "Lando,Michael" 
CC: meng.zhaoxi...@zte.com.cn, yuan@zte.com.cn
Subject: Re:CSAR from SDC


Hi Michael,


We get a couple of questions here after studying the example.


1. Can't find the corresponding node template for the defined capabilities and 
requirements in the substitution_mappings


For example:

 The substitution_mappings defined in the 
service-57431726F7e64a30Ae52-template.yml of service-vvg.csar


tosca_definitions_version: tosca_simple_yaml_1_0

# omitted here for brevity

topology_template:

  node_templates:

d7c95393-7396-4d74-a3b0 0:

  type: org.openecomp.resource.vf.D7c9539373964d74A3b0

  metadata:

invariantUUID: 7564e792-a8af-4f73-9910-2e3b88dfa862

UUID: 31d208bc-9744-4060-baa8-2decca503193

customizationUUID: 2f9f65ab-6aef-48fc-a63f-5ac96e88c0ad

version: '1.0'

name: d7c95393-7396-4d74-a3b0

description: vendor software product

type: VF

category: Generic

subcategory: Abstract

resourceVendor: 06715d78-893c-4a45-88c1

resourceVendorRelease: '1.0'

# omitted here for brevity

  substitution_mappings:

node_type: org.openecomp.service.57431726F7e64a30Ae52

capabilities:

  d7c9539373964d74a3b00.cinder_volume.feature:

  - cinder_volume

  - cinder_volume.feature

  d7c9539373964d74a3b00.cinder_volume.attachment:

  - cinder_volume

  - cinder_volume.attachment

requirements:

  d7c9539373964d74a3b00.cinder_volume.dependency:

  - cinder_volume

  - cinder_volume.dependency


2. Does SDC support the definition of  TOSCA Group?

3. Does SDC support the definition of TOSCA  Policy?

4. Does SDC support the mapping of Input and Node Template property?

5. Does SDC support the mapping of Output and Node Template attribute?


Thanks,

Huabing







Original Mail
Sender:  
To: zhaohuabing10201488
Date: 2017/07/11 22:36
Subject: CSAR from SDC

Hi,
As discussed today on the call.
I am attaching the scar created for the 3 services part of the uses case 
currently supported.


BR,

Michael Lando
Opensource & Frontend Team Lead, SDC
AT Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
···
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: ml6...@intl.att.com___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] [ptls][cli][msb][aaf] Review ONAPfunctionalites to support from CLI

[zhao.huabing]

Hi Kanagaraj,




Sure. 

Currently, we're mainly using the AAF weekly meeting to discuss the integration 
between AAF and MSB.

The conclusion of the last meeting is that AAF will add a Lua plugin which can 
provide centralized auth at the MSB external API  gateway.




I will add you in the loop for theurther discussion.




BR,

Huabing






Original Mail



Sender:  
To:   
CC:     
 
Date: 2017/07/17 21:51
Subject: Re: [onap-discuss] [onap-tsc] [ptls][cli][msb][aaf] Review 
ONAPfunctionalites to support from  CLI







Dear Huabing,


 


CLI project would depends on the MSB for service discovery and AAF for AA. So I 
have gone thru  the MSB release planning from wiki and found that your are 
planning to integrate AAF as one of the Auth service  provider in MSB.


IMO, It’s an right integration and as CLI also would get impacted (for AA), I 
would like to participate the discussion around this integration. Could you 
please keep me in the loop. Thanks.


 


Regards


Kanagaraj M


 


***
 
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**
 
***
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
***



 



From: 杨艳 [mailto:yangya...@chinamobile.com] 
 Sent: Monday, July 17, 2017 9:27 AM
 To: Kanagaraj Manickam onap-discuss@lists.onap.org
 Cc: rk5...@att.com ah0...@intl.att.com gg2...@att.com es4...@att.com 
sw3...@att.com onap-...@lists.onap.org
 Subject: 答复: [onap-tsc] [ptls][cli] Review ONAP functionalites to support from 
CLI




 


Sorry for late response. There is no problem from my perspective.


 


Regards,


Yan



发件人: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com] 
 发送时间: 2017年7月13日  22:41
 收件人: 杨艳 onap-discuss@lists.onap.org
 抄送: rk5...@att.com ah0...@intl.att.com gg2...@att.com es4...@att.com 
sw3...@att.com onap-...@lists.onap.org
 主题: RE: [onap-tsc] [ptls][cli] Review ONAP functionalites to  support from CLI




 


Hi Yan,


 


Thanks for reviewing.


I tried add related projects for every feature listed in the wiki. For example, 
VNFM and EMS are used by VFC but are on-boarded  using A/ESR, So mentioned 
VFC as well.


As it creates confusion on the project column, I updated the wiki to keep only 
the dependent project, which provides the functionalities.


Could you please review it once? Thanks.


 


Regards


Kanagaraj M


 


 


***
 
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**
 
***
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
***



 



From: 杨艳 [mailto:yangya...@chinamobile.com] 
 Sent: Thursday, July 13, 2017 12:07 PM
 To: Kanagaraj Manickam onap-discuss@lists.onap.org
 Cc: rk5...@att.com ah0...@intl.att.com gg2...@att.com es4...@att.com 
sw3...@att.com onap-...@lists.onap.org
 Subject: 答复: [onap-tsc] [ptls][cli] Review ONAP functionalites to support from 
CLI




 


Hi Kanagaraj,


 


I read the wiki page you mentioned, for the External Resource Management part, 
VFC has been listed in the VNFM and EMS management, I’m not very clear what the 
meaning of the projects list here, but I would like to clarify that VF-C will 
only use the  information  of VNFM and  EMS as a consumer, such as url, user 
name, etc.


 


 


Regards,

[onap-discuss] Reply： [modeling] Please vote for chairperson of ModelingSubcommittee

[zhao.huabing]

+1






 

 Original Message
 
 

 

 

 

 
 From:
 denghui(L) 
 

 
 To:onap-...@lists.onap.org onap-discuss@lists.onap.org 
 

 
 Date:
 2017-07-07 11:57:07
 

 
 Subject:[onap-discuss] [modeling] Please vote for chairperson of 
ModelingSubcommittee
 

 

 
 
 
 
 
 


 
 
 
Hello, Modelling members,
 

 
 

 
  
 

 
 
There is only one candidate for modeling subcommittee: Hui Deng
 

 
 

 
  
 

 
 
If you support Please help to vote “+1”, 
 
 

 
 
If you are neutral, please vote “0”,
 

 
 
If you don’t please respond  “-1” 
 

 
 

 
  
 

 
 
Members are listed here: https://wiki.onap.org/display/DW/Members
 

 
 

 
  
 

 
 
Thanks a lot
 

 
 

 
  
 

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

Re: [onap-discuss] OOM PTL Poll Result

[zhao.huabing]

Hi David,




I'm interested in the OOM project and I'd like to contribute this part of codes 
to connect OOM with MSB, so the service end points could be registered to MSB 
after ONAP components have been spin up by OOM.

Do we have ONAP weekly meeting set up yet? If we do, Could you please add this 
to the agenda of this week's meeting?


I looped John in. We have talked at the MSB Kickoff meeting, He would like to 
know the progress of the cooperation between MSB and OOM.




Thanks,

Huabing






Original Mail



Sender:  
To:   
Date: 2017/06/29 03:24
Subject: Re: [onap-discuss] OOM PTL Poll Result







Thanks all!


 


I will be setting up weekly meetings with the LF.


 


We have also uploaded seed code that we can start working from together! A 
Kubernetes/docker demo for installing key onap components is also available, so 
let me know if you are interested.


 



From:  on behalf of "HU, JUN NICOLAS" 

 Date: Monday, June 26, 2017 at 9:31 AM
 To: "onap-discuss@lists.onap.org" 
 Subject: [onap-discuss] OOM PTL Poll Result



 

Hi there,

I'd like to share with you that the OOM PTL poll has been ended according to 
the planned poll period and the elected PTL is David Sauvageau.

Poll result: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4516726d2434dd38

Congratulations David.


 


Jun Nicolas Hu
 SR MEMBER OF TECHNICAL STAFF


AT


Email : jun.nicolas...@att.com


Office : +1 (732) 420-0743


200 S Laurel Ave, Rm D5-3B34


Middletown, NJ 08873


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

Re: [onap-discuss] Discuss Dmaap Integration into MSB

[zhao.huabing]

Hi Pam,

It's a very good suggestion. We have talked about this at the MSB kickoff 
meeting.  https://wiki.onap.org/display/DW/MSB+Meeting-2017-07-03  

I will add it as a stretch goal for the MSB project. It may be helpful if you 
could give an example so we can better understand the difficult Policy project 
faced and start the discussion for the solution.




Thanks,

Huabing



Original Mail



Sender:  
To:  
Date: 2017/07/03 22:04
Subject: [onap-discuss] Discuss Dmaap Integration into MSB







Hi,


 


I would like to propose a discussion on whether it makes sense to have Dmaap 
integrated into the MSB Project for discovery of Dmaap topics in addition to 
RESTful API’s.


 


Currently it is a little difficult for the Policy Platform to configure BOTH 
RESTful API access as well as Dmaap Topic details into our platform during 
deployment. The MSB Project (and OOM) seems to be a great  step towards making 
it easier for our components to come up and discover RESTful API and would like 
to see the same ability applied to Dmaap topics.


 


Can folks weigh in on this as a possibility? Perhaps not viable for R1, but at 
least get the discussion going for possible inclusion on the long term roadmap?


 


Pam Dragosh


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

[onap-discuss] [MSB] MSB kickoff meeting minutes

[zhao.huabing]

Hi,



Thanks for attending our kickoff meeting.



The minutes and slides have been put to this wiki page.



https://wiki.onap.org/display/DW/MSB+Meeting-2017-07-03



Thanks,

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

Re: [onap-discuss] OOM PTL Poll Result

[zhao.huabing]

Hi David,




Please also loop me in so we can discuss how OOM and MSB can work together for 
service endpoints registration.




Thanks,

Huabing










Original Mail



Sender:  
To:  
CC:  
Date: 2017/06/29 19:26
Subject: Re: [onap-discuss] OOM PTL Poll Result





Hi Viswa

Welcome! We will have a demo of what is available on the seed code and discuss 
milestone planning on our first weekly meeting next week. Trying to get the LF 
to send an invite 

Thanks!
 
 Envoyé de mon iPhone

 Le 29 juin 2017 à 03:41, Viswa KSP  a écrit :
 
 

Hi David,

 

I'm Viswa from Verizon and interested in joining this efforts.


 

Please have me looped in.


 

BR,

Viswa



 
On Jun 29, 2017 12:53 AM, "Sauvageau, David"  wrote: 


Thanks all!


 


I will be setting up weekly meetings with the LF.


 


We have also uploaded seed code that we can start working from together! A 
Kubernetes/docker demo for installing key onap components is also available, so 
let me know if you are interested.


 



From:  on behalf of "HU, JUN NICOLAS" 

 Date: Monday, June 26, 2017 at 9:31 AM
 To: "onap-discuss@lists.onap.org" 
 Subject: [onap-discuss] OOM PTL Poll Result



 


Hi there,

I'd like to share with you that the OOM PTL poll has been ended according to 
the planned poll period and the elected PTL is David Sauvageau.

Poll result: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4516726d2434dd38

Congratulations David.


 


Jun Nicolas Hu
 SR MEMBER OF TECHNICAL STAFF


AT


Email : jun.nicolas...@att.com


Office : +1 (732) 420-0743


200 S Laurel Ave, Rm D5-3B34


Middletown, NJ 08873


USA


 




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

[onap-discuss] MSB PTL Poll Result //Re:Election started //Re: [MSB] Call for Microservices Bus Project PTL Nominations

[zhao.huabing]

Hi there,





I'd like to share with you that the MSB PTL poll has been ended according to 
the planned poll period and the elected PTL is Huabing Zhao(myself).




Poll result: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_79dac21fe9d0c305




Thanks for your support. I appreciate it.  Later I will send out a doodle poll 
to find a timeslot for our kickoff meeting.




Huabing



Original Mail



Sender: zhaohuabing10201488
To:  
Date: 2017/06/22 09:34
Subject: Election started //Re:[onap-discuss] [MSB] Call for Microservices Bus 
Project PTL Nominations







Dear MSB committers,


 


I would like to inform you that the poll has been set up for MSB PTL and 
available for you to vote.


 


The poll will be closed on June 26.


 


Regards,


Huabing
















Sender: zhaohuabing10201488
To:  
Date: 2017/06/17 11:27
Subject: [onap-discuss] [MSB] Call for Microservices Bus Project PTL Nominations






Greetings MSB Committers,

 

The Microservices Bus project is soliciting self-nominations for its Project 
Technical Lead.  Per TSC instructions, nominees should be from those listed as 
committers on the Microservices Bus project proposal approved by the ONAP TSC 
(https://wiki.onap.org/pages/viewpage.action?pageId=3246982).

The nomination period will end on Tuesday, June 20.

 

To nominate, please send an email to the onap-discuss list, stating your 
interest, and a short bio for helping people to know you better. 

After the nomination period is closed, a voting poll will be set up for vote 
collection.

 

Have a nice weekend!

 

Thanks & regards

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