from:"Seshu m"

Re: [onap-discuss] Generic SO BPMN Flow for HEAT orchestration

2018-06-18 Thread Seshu m

Hi Mandeep,

Yes, we have alacarte recipies in place now that are introduced as a part of 
the Beijing.
We also have custom flows that you can refer to for the other usecases.
ONAP as a platform would be able to perform orchestration based on the kind of 
recipe you feed.

ARIA orchestration is not fully functional (tested) in SO as of Beijing release.

Thanks and Regards,
M Seshu Kumar
Senior System Architect
uTraffic, Software BU,
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka.
Tel: + 91-80-49160700 , Mob: 9845355488
___
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 [onap-discuss-boun...@lists.onap.org] 
on behalf of Singh Kalra, Mandeep [mandeep.singh.ka...@accenture.com]
Sent: Thursday, June 14, 2018 11:30 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Generic SO BPMN Flow for HEAT orchestration

Hi,

  I had a doubt about the orchestration of some use cases like vFW, vCPE  
in which HEAT templates are used.
  In the demo as part of R1, VID was used to create the Service in which 
first the service was created then VNF and then VF modules.

 Is there a generic flow available in R2 in which we can pass a single 
request from the northbound system ?
 And is ARIA orchestration integrated with SO ?




Regards
Mandeep



This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise confidential information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the e-mail by you is prohibited. Where allowed by local law, electronic 
communications with Accenture and its affiliates, including e-mail and instant 
messaging (including content), may be scanned by our systems for the purposes 
of information security and assessment of internal compliance with Accenture 
policy. Your privacy is important to us. Accenture uses your personal data only 
in compliance with data protection laws. For further information on how 
Accenture processes your personal data, please see our privacy statement at 
https://www.accenture.com/us-en/privacy-policy.
__

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

Re: [onap-discuss] [coe] Meeting's time update

2018-06-05 Thread Seshu m

Hi Guys,

Couldnt make it to the meeting, could smeone ping the MOM details link.
Thanks in advance

Thanks and Regards,
M Seshu Kumar
Senior System Architect
uTraffic, Software BU,
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka.
Tel: + 91-80-49160700 , Mob: 9845355488
___
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: Addepalli, Srinivasa R [srinivasa.r.addepa...@intel.com]
Sent: Tuesday, June 05, 2018 10:37 PM
To: Morales, Victor; onap-discuss@lists.onap.org; Munish Agarwal; Shankar, 
Shashank Kumar; Ramki Krishnan; Seshu m; Yeleswarapu, Ramamani; HU, BIN
Subject: RE: [coe] Meeting's time update

Hi Victor,

Let us discuss today.  But, I thought I will provide my initial thoughts on the 
scope of the K8S plugin activities:


1.  Defining the API between Multi-Cloud & Test SO/VF-C : WE can get some 
ideas from SOL003 and follow this API as much as possible.  WE just need to 
implement only subset of the API for this POC.  One good thing to follow this 
API is that when SO moves to support SOL003 VNFMs,  there would be minimal 
changes in SO to support Multi-Cloud API.  We also may need to add some 
additional elements to JSON body of these API requests to pass artifact 
references, other meta data (such as cloud region ID and compute profiles for 
the VNF etc…)

a.  APIs:

i. Instantiate VNF

   ii. Terminate VNF 
instance

  iii. Identify others that 
are MUST.

  iv. Scale-out, Other VNF 
LCMs can be done later.

2.  Multi-Cloud broker changes to accept above API and passing those API 
requests to right plugin (in this case K8S plugin and in future more plugins 
are possible).

3.  K8S Plugin:

a.  K8S site registration related changes (if any) : Is ESR registration of 
cloud-region good enough or are any changes required in that?

b.  Onboard time:

i. Getting hold of 
artifacts from SDC and storing them locally.

c.  Run time:

i. As part of VNF 
instantiation:

1.  Ability to refer to artifacts from the references.

2.  Translation from artifacts + metadata to

a.  Set of K8S API (for compute and storage)

b.  Set of OVN API (for networking)

c.  Other CNIs (if time permits)

3.  Getting the result and adding the result to A DB. (Need to check if 
there are any changes required there)

On Kubernetes reference cloud:

-We will go with bare-metal container clouds for now.

-Supporting Azure/GCP/IBM/AWS container support is for future.

-Cloud stack to have:

o   K8S

o   OVN

o   Virtlet

o   SRIOV (if time permits)

o   Flannel (if time permits)

-EdgeXFoundry containers

-Firewall VM

-Router Container image creation.

Thanks
Srini


From: Morales, Victor
Sent: Monday, June 4, 2018 4:49 PM
To: Addepalli, Srinivasa R ; 
onap-discuss@lists.onap.org; Munish Agarwal ; 
Shankar, Shashank Kumar ; Ramki Krishnan 
; Seshu m ; Yeleswarapu, Ramamani 
; HU, BIN 
Subject: Re: [coe] Meeting's time update

Good idea Srini,

I started doing the breakdown of the activities for this project. From my 
perspective, there are two main efforts:


1.  MultiCloud/k8s plugin:

2.  Kubernetes Reference Deployment

Therefore, the agenda for tomorrow’s meeting is:


·Definition and scope of previous two efforts.

·Initial draft of the activities identified.

·Virtlet or KubeVirt?

·Swagger API or OpenAPI

Regards,
Victor Morales

From: "Addepalli, Srinivasa R" 
mailto:srinivasa.r.addepa...@intel.com>>
Date: Monday, June 4, 2018 at 4:25 PM
To: Victor Morales mailto:victor.mora...@intel.com>>, 
"onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>, Munish 
Agarwal mailto:munish.agar...@ericsson.com>>, 
"Shankar, Shashank Kumar" 
mailto:shashank.kumar.shan...@

[onap-discuss] Pairwise testing passed SO and OOF is successful

2018-06-01 Thread Seshu m

Dear Gildas,

Happy to announce that, We have successfully tested the SO and OOF interface on 
the OOM (SB-00) env.
With this both SO and OOF teams have completed the tasks in hand for RC2 and 
will be making the final release versions of the dockers.
As aniticipated the issue was in the configuration of the OOM that created the 
issue initially.
Special thanks to the OOF team for rendering the late night support in making 
this work.

The dashboard has been updated with the latest status
https://wiki.onap.org/display/DW/Integration+Weather+Board


Thanks and Regards,
M Seshu Kumar
Senior System Architect
uTraffic, Software BU,
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka.
Tel: + 91-80-49160700 , Mob: 9845355488
___
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: PUZHAVAKATH NARAYANAN, SHANKARANARAYANAN (SHANKARANARAYANAN) 
[snaraya...@research.att.com]
Sent: Friday, June 01, 2018 2:28 PM
To: Seshu m
Subject: Fwd: Pairwise testing OOM logs



Begin forwarded message:

From: "PATEL, ANKITKUMAR N (ANKITKUMAR N)" 
mailto:an...@research.att.com>>
Subject: Pairwise testing OOM logs
Date: June 1, 2018 at 2:22:21 AM EDT
To: "PUZHAVAKATH NARAYANAN, SHANKARANARAYANAN (SHANKARANARAYANAN)" 
mailto:snaraya...@research.att.com>>
Cc: "PUTHENPURA, SARAT (SARAT)" 
mailto:sa...@research.att.com>>

Please find an evidence for completing the pairwise testing in the OOM 
environment.

Debug Logs


2018-06-01T06:13:14,229+00:00||Thread-12||OOF_OSDF|b52461cc-6562-11e8-95f1-02ba2e87b068|DEBUG||10.42.200.221|dev-oof-6585965cfc-g6hxqRequesting
 URL: http://pdp:8081/pdp/api/getConfig
2018-06-01T06:13:14,302+00:00||Thread-12||OOF_OSDF|b52461cc-6562-11e8-95f1-02ba2e87b068|DEBUG||10.42.200.221|dev-oof-6585965cfc-g6hxqReceived
 response [code: 200, headers: {'Server': 'Apache-Coyote/1.1', 'Content-Type': 
'application/json;charset=UTF-8', 'Date': 'Fri, 01 Jun 2018 06:13:17 GMT', 
'Transfer-Encoding': 'chunked'}, data: {'history': [], '_content': 
b'[{"policyConfigMessage":"Config Retrieved! 
","policyConfigStatus":"CONFIG_RETRIEVED","type":"JSON","config":"{\\"service\\":\\"optimizationQueryPolicy\\",\\"policyName\\":\\"OSDF_R2.QueryPolicy_vCPE\\",\\"description\\":\\"Optimization
 query policy for 
vCPE\\",\\"templateVersion\\":\\"OpenSource.version.1\\",\\"version\\":\\"test1\\",\\"priority\\":\\"3\\",\\"riskType\\":\\"test\\",\\"riskLevel\\":\\"2\\",\\"guard\\":\\"False\\",\\"content\\":{\\"queryProperties\\":[{\\"attribute\\":\\"customerLatitude\\",\\"attribute_location\\":\\"customerLatitude\\"},{\\"attribute\\":\\"customerLongitude\\",\\"attribute_location\\":\\"customerLongitude\\"}],\\"policyScope\\":[\\"vcpe\\",\\"us\\",\\"international\\",\\"ip\\",\\"vgmuxar\\",\\"vgw\\"],\\"policyType\\":\\"optimizationQueryPolicy\\",\\"serviceName\\":\\"vCPE\\",\\"identity\\":\\"vCPE_Query_Policy\\"}}","policyName":"OSDF_R2.Config_OOF_QueryPolicy_vCPE.1.xml","policyType":"Optimization","policyVersion":"1","matchingConditions":{"ONAPName":"DCAE","service":"optimizationQueryPolicy","policyScope":"vcpe,us,international,ip,vgmuxar,vgw","policyType":"optimizationQueryPolicy"},"responseAttributes":{},"property":null},{"policyConfigMessage":"Config
 Retrieved! 
","policyConfigStatus":"CONFIG_RETRIEVED","type":"JSON","config":"{\\"service\\":\\"vnfPolicy\\",\\"policyName\\":\\"OSDF_R2.vnfPolicy_vGW\\",\\"description\\":\\"

Re: [onap-discuss] [ONAP Helpdesk #56363] [linuxfoundation.org #56363] RE: Issue with the Doc verify build time out

2018-05-23 Thread Seshu m

OK,  thanks for the update.
I could see the current current build is success.
https://jenkins.onap.org/job/doc-master-verify-rtd/2213/


Thanks and Regards,
M Seshu Kumar
Senior System Architect
uTraffic, Software BU,
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka.
Tel: + 91-80-49160700 , Mob: 9845355488
___
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: BENNETT, RICH via RT [onap-helpd...@rt.linuxfoundation.org]
Sent: Thursday, May 24, 2018 1:10 PM
To: Seshu m
Cc: gg2...@att.com; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [ONAP Helpdesk #56363] [linuxfoundation.org #56363] 
RE: Issue with the Doc verify build time out

Seshu,

We are proceeding with option 1, increase the submodule clone timeout.  Patch  
https://gerrit.onap.org/r/#/c/48851/ is pending review.

Neither the scm-repo-depth or scm-git-shallow-clone apply to submodules, but we 
will continue to investigate if there is jjb support for submodule shallow 
clones to reduce the size (from 700MB to 3MB) and time to clone the large 
repository.

Thank you

Rich


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

[onap-discuss] Issue with the Doc verify build time out

2018-05-23 Thread Seshu m

Dear Greg/LF team,

https://jenkins.onap.org/job/doc-master-verify-rtd/2204/console

I see a timeout occuring in the doc master verify which is failing our changes 
to the project specific documentation.

Request to kindly help us in the resolution.

Thanks and Regards,
M Seshu Kumar
Senior System Architect
uTraffic, Software BU,
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka.
Tel: + 91-80-49160700 , Mob: 9845355488
___
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] [so] mso:1.2.1 image missing

2018-05-18 Thread Seshu m

Hi Gary

This is strange why things go missing,
I triggered a new build and I can see the Docker back
https://nexus3.onap.org/#browse/search=keyword%3Dmso:7f6379d32f8dd78fd8e42923c8ff348e:88bfafa960bab52124a30fecfc044940
[cid:image001.png@01D3EEBC.1BCABC50]

http://12.234.32.117/jenkins/job/nexus3-docker-image-check/157/
is success..

Thanks and Regards,
M Seshu Kumar
Senior System Architect
Single OSS India Branch Department. S/W BU.
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka.
Tel: + 91-80-49160700 , Mob: 9845355488
[Company_logo]
___
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 Gary Wu
Sent: Friday, May 18, 2018 1:28 PM
To: helpd...@onap.org; onap-discuss@lists.onap.org
Subject: [onap-discuss] [so] mso:1.2.1 image missing

Hi helpdesk and/or the SO team,

Currently the mso image is missing:

22:05:48 [ERROR] openecomp/mso:1.2.1 not found
http://12.234.32.117/jenkins/job/nexus3-docker-image-check/155/console

Can we figure out what happened?  This will likely cause problems for upcoming 
deployments.

Thanks,
Gary


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

Re: [onap-discuss] [MSO] How to enable camunda groovy process logs

2018-05-15 Thread Seshu m

Hi Chandra

Hope you have already tried out these ways.

The DEBUG mode is enabled by module and has to be re-enabled if the application 
restart.
It can be enabled by the following APIs:

  *   To enable logging on Camunda (no authentication):
 *   GET on 
http://c1.vm1.mso.simpledemo.openecomp.org:8080/mso/logging/debug
  *   To enable logging on APIH (use any jboss user with role CSI-Client for 
authentication):
 *   GET on 
http://c1.vm1.mso.simpledemo.openecomp.org:8080/ecomp/mso/logging/debug
  *   To enable logging on APIH Homing (use any jboss user with role CSI-Client 
for authentication):
 *   GET on 
http://c1.vm1.mso.simpledemo.openecomp.org:8080/ecomp/mso/homing/logging/debug
  *   To enable logging on APIH Infra (use any jboss user with role 
InfraPortal-Client for authentication):
 *   GET on 
http://c1.vm1.mso.simpledemo.openecomp.org:8080/ecomp/mso/infra/logging/debug
  *   To enable logging on ASDC (no authentication):
 *   GET on 
http://c1.vm1.mso.simpledemo.openecomp.org:8080/asdc/logging/debug
  *   To enable logging on DBAdapter (no authentication):
 *   GET on 
http://c1.vm1.mso.simpledemo.openecomp.org:8080/dbadapters/logging/debug
  *   To enable logging on Network adapter (no authentication):
 *   GET on 
http://c1.vm1.mso.simpledemo.openecomp.org:8080/networks/rest/logging/debug
  *   To enable logging on SDNC adapter (use any jboss user with role 
MSO-Client for authentication):
 *   GET on 
http://c1.vm1.mso.simpledemo.openecomp.org:8080/adapters/rest/logging/debug
  *   To enable logging on VNF adapter (no authentication):
 *   GET on 
http://c1.vm1.mso.simpledemo.openecomp.org:8080/vnfs/rest/logging/debug
  *   To enable logging on Tenant adapter (no authentication):
 *   GET on 
http://c1.vm1.mso.simpledemo.openecomp.org:8080/tenants/rest/logging/debug
  *   To enable logging on APPC adapter (no authentication):
 *   GET on 
http://c1.vm1.mso.simpledemo.openecomp.org:8080/appc/rest/logging/debug

There are ways to debug the information while running from groovy.
Logging being one option the other could be through the remote debug using the 
standard IDE.
If you could let me know what exact operation you are stuck at I could perhaps 
provide some help.

Thanks and Regards,
M Seshu Kumar
Senior System Architect
uTraffic, Software BU,
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka.
Tel: + 91-80-49160700 , Mob: 9845355488
___
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: Chandrashekhar Thakare [ct00548...@techmahindra.com]
Sent: Tuesday, May 15, 2018 6:02 PM
To: Subhash Kumar Singh; onap-discuss@lists.onap.org
Cc: Seshu m; Praveen Krishnamurthy P
Subject: RE: [MSO] How to enable camunda groovy process logs

Hi Subhash,
Thanks for your response. We have followed the document and enabled the debug 
logs. However we are unable to see groovy  debug logs  captured.

We are carrying out some analysis over VF creation, createVFmoduleInfra.groovy. 
The debug logs are not captured in any of the logs.

Regards
Chandu


From: Subhash Kumar Singh [mailto:subhash.kumar.si...@huawei.com]
Sent: Tuesday, May 15, 2018 2:01 PM
To: Chandrashekhar Thakare <ct00548...@techmahindra.com>; 
onap-discuss@lists.onap.org
Cc: Seshu m <seshu.kuma...@huawei.com>; Praveen Krishnamurthy P 
<kprav...@huawei.com>
Subject: RE: [MSO] How to enable camunda groovy process logs

Hello Chandrashekhar,

You can try to send Get query to :
Camunda (no authentication): http:/:8080/mso/logging/debug<http://c1.vm1.mso.simpledemo.onap.org:8080/mso/logging/debug>
 [1]

This will enable groovy debug logs.

[1] https://github.com/onap/so#eelf

--
Subhash Kumar Singh
Technical Project Leader
FNOSS, ONAP

Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka
Tel: Mob: 8050101106 Email: 
subhash.kumar.si...@huawei.com<mailto:subhash.kumar.si...@huawei.com>
[Company_logo]




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
informati

Re: [onap-discuss] License for docker-compose.yml

2018-05-09 Thread Seshu m

Hi Steve,
I was of the impression that placing a License.txt file with the Apache License 
would be sufficient for cases like these.
Correct me if this is not the case?

Thanks and Regards,
M Seshu Kumar
Senior System Architect
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka.
Tel: + 91-80-49160700 , Mob: 9845355488
[Company_logo]
___
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 DRAGOSH, PAMELA L 
(PAM)
Sent: Wednesday, May 09, 2018 8:13 PM
To: eric.deb...@orange.com; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] License for docker-compose.yml

Eric,

I have the same question.

Also, now the .gitignore, .gitreview and INFO.yaml files are included in the 
scan. Really? These need to be done also?

Pam


From:  on behalf of 
"eric.deb...@orange.com" 
Date: Wednesday, May 9, 2018 at 8:08 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] License for docker-compose.yml

Hello

Following feedbacks from Linux Foundation, the last license scan detected that 
docker-compose.yml does not contain license. Do we need to put a license in 
docker-compose.yml file ?

In general, where are defined the rules to exclude some files with license 
issues ?

Best Regards

Eric

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

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

[onap-discuss] Issue with the build process

2018-04-19 Thread Seshu m

Dear LF

The current jenkins capacity seems insufficient to handle the build jobs.
Could we please increase this to make it more productive.

Best Regards,
Seshu
**
 This email 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 here 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 
email 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] Regarding Tosca parsing of Overlay/Underlay templates for VoLTE use case

2018-04-12 Thread Seshu m

if and when added, This will be part of the SDNC adapter and can be used for 
any usecase based on need.
But, nothing is yet planned to use this as of now.

Best Regards,
Seshu
**
 This email 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 here 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 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*

From: Singh Kalra, Mandeep [mandeep.singh.ka...@accenture.com]
Sent: Friday, April 13, 2018 12:28 PM
To: Seshu m; Chenchuanyu; Ramu n; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Regarding Tosca parsing of Overlay/Underlay 
templates for VoLTE use case

Thanks Seshu.

Is it applicable for volte use case or other cases as well ?


Regards
Mandeep
From: Seshu m [mailto:seshu.kuma...@huawei.com]
Sent: Friday, April 13, 2018 9:55 AM
To: Singh Kalra, Mandeep <mandeep.singh.ka...@accenture.com>; Chenchuanyu 
<chenchua...@huawei.com>; Ramu n <ram...@huawei.com>; 
onap-discuss@lists.onap.org
Subject: [External] RE: [onap-discuss] Regarding Tosca parsing of 
Overlay/Underlay templates for VoLTE use case

HI Mandeep,

The SDNC notifications are not yet used now, currently we are workng on makng 
the workflows more generic and SO to support functional requirements.
We would be considering this in the later releases.

Best Regards,
Seshu
**
 This email 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 here 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 
email 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> 
[onap-discuss-boun...@lists.onap.org] on behalf of Singh Kalra, Mandeep 
[mandeep.singh.ka...@accenture.com]
Sent: Friday, April 13, 2018 11:58 AM
To: Chenchuanyu; Ramu n; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] Regarding Tosca parsing of Overlay/Underlay 
templates for VoLTE use case
Hi Chuanyu,

 Thanks.
 Is SO having the sdnc notify mechanism and based 
on that update the resource operation status table for volte use case so that 
we could fetch the exact status?
 I can see that SDNC operations 
service-topology-operation/network-topology-operation are called from the 
serviceTask now, is there any plan to introduce the notification mechanism 
there or use sdnc adapter in future ?


Regards
Mandeep

From: Chenchuanyu [mailto:chenchua...@huawei.com]
Sent: Monday, March 19, 2018 7:09 AM
To: Singh Kalra, Mandeep 
<mandeep.singh.ka...@accenture.com<mailto:mandeep.singh.ka...@accenture.com>>; 
Ramu n <ram...@huawei.com<mailto:ram...@huawei.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [External] 答复: [onap-discuss] Regarding Tosca parsing of 
Overlay/Underlay templates for VoLTE use case

Hi Mandeep,
   As I know, SDC  have not changed the model for voLTE until now, both with NS 
and overlay/underlay .
  Now WAN model is still under discussion by modeling team. So we will wait for 
the conclusion.
  For SO part ,  we only make the bpmn workflow more generic for E2E service. 
such as calling the e2e service recipe, decompose the model and so on. In R1, 
the workflow is specific for voLTE.
Thanks,
Chuanyu Chen.

发件人: Singh Kalra, Mandeep [mailto:mandeep.singh.ka...@accenture.com]
发送时间: 2018年3月17日 23:01
收件人: Chenchuanyu; Ramu n; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
主题: RE: [onap-discuss] Regarding Tosca parsing of Overlay/Underlay templates 
for VoLTE use case

Thanks a lot Chuanyu and Ramu .

@Chunuyu :: I can see that there are some updates done to SO bpmn scripts in 
master branch for VoLTE case, is this change of parsing the overlay/underlay 
templates part already there ?

How about the modelling in SDC, will that also be changed ? PNFs etc for 
underlay ?

@Ramu :: Is there any change i

Re: [onap-discuss] Regarding Tosca parsing of Overlay/Underlay templates for VoLTE use case

2018-04-12 Thread Seshu m

HI Mandeep,

The SDNC notifications are not yet used now, currently we are workng on makng 
the workflows more generic and SO to support functional requirements.
We would be considering this in the later releases.

Best Regards,
Seshu
**
 This email 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 here 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 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*

From: onap-discuss-boun...@lists.onap.org [onap-discuss-boun...@lists.onap.org] 
on behalf of Singh Kalra, Mandeep [mandeep.singh.ka...@accenture.com]
Sent: Friday, April 13, 2018 11:58 AM
To: Chenchuanyu; Ramu n; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Regarding Tosca parsing of Overlay/Underlay 
templates for VoLTE use case

Hi Chuanyu,

 Thanks.
 Is SO having the sdnc notify mechanism and based 
on that update the resource operation status table for volte use case so that 
we could fetch the exact status?
 I can see that SDNC operations 
service-topology-operation/network-topology-operation are called from the 
serviceTask now, is there any plan to introduce the notification mechanism 
there or use sdnc adapter in future ?


Regards
Mandeep

From: Chenchuanyu [mailto:chenchua...@huawei.com]
Sent: Monday, March 19, 2018 7:09 AM
To: Singh Kalra, Mandeep ; Ramu n 
; onap-discuss@lists.onap.org
Subject: [External] 答复: [onap-discuss] Regarding Tosca parsing of 
Overlay/Underlay templates for VoLTE use case

Hi Mandeep,
   As I know, SDC  have not changed the model for voLTE until now, both with NS 
and overlay/underlay .
  Now WAN model is still under discussion by modeling team. So we will wait for 
the conclusion.
  For SO part ,  we only make the bpmn workflow more generic for E2E service. 
such as calling the e2e service recipe, decompose the model and so on. In R1, 
the workflow is specific for voLTE.
Thanks,
Chuanyu Chen.

发件人: Singh Kalra, Mandeep [mailto:mandeep.singh.ka...@accenture.com]
发送时间: 2018年3月17日 23:01
收件人: Chenchuanyu; Ramu n; 
onap-discuss@lists.onap.org
主题: RE: [onap-discuss] Regarding Tosca parsing of Overlay/Underlay templates 
for VoLTE use case

Thanks a lot Chuanyu and Ramu .

@Chunuyu :: I can see that there are some updates done to SO bpmn scripts in 
master branch for VoLTE case, is this change of parsing the overlay/underlay 
templates part already there ?

How about the modelling in SDC, will that also be changed ? PNFs etc for 
underlay ?

@Ramu :: Is there any change in SDNC’s directed graphs for this case ?


Regards
Mandeep



From: Chenchuanyu [mailto:chenchua...@huawei.com]
Sent: Wednesday, February 28, 2018 2:38 PM
To: Singh Kalra, Mandeep 
>; 
Ramu n >; 
onap-discuss@lists.onap.org
Subject: [External] 答复: [onap-discuss] Regarding Tosca parsing of 
Overlay/Underlay templates for VoLTE use case

Hi, Mandeep,
  SO will do this(but in R1, this have not been implemented, all parameters 
published as user inputs).
  In R2, SO will merge both user filled parameters and template assigned 
parameters(which set in design time), and then sent all of them to SDNC.
Thanks,
Chuanyu Chen.

发件人: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] 代表 Singh Kalra, Mandeep
发送时间: 2018年2月28日 17:02
收件人: Ramu n; onap-discuss@lists.onap.org
主题: Re: [onap-discuss] Regarding Tosca parsing of Overlay/Underlay templates 
for VoLTE use case

Thanks Ramu.

I guess UUI will only take the input parameters from the users.
In case the template also holds some values, who will be parsing/providing that 
?

And can you please share the AAI - SDNC configurations for the VoLTE use case. 
Does SDNC itself holds some data apart from AAI ?


Regards
Mandeep

From: Ramu n [mailto:ram...@huawei.com]
Sent: Wednesday, February 28, 2018 2:06 PM
To: Singh Kalra, Mandeep 
>; 
onap-discuss@lists.onap.org
Subject: [External] RE: [onap-discuss] Regarding Tosca parsing of 
Overlay/Underlay templates for VoLTE use case

Hi Mandeep,

For VoLTE use case,

Re: [onap-discuss] [aai] [so] aai-common 1.2.0 depends on expired oparent snapshot

2018-03-26 Thread Seshu m

HI Marcus,

Jimmy is already working towards resolving this issue.
Thanks for the mail.

Best Regards,
Seshu
**
 This email 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 here 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 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*

From: Williams, Marcus [marcus.willi...@intel.com]
Sent: Tuesday, March 27, 2018 4:26 AM
To: onap-discuss
Cc: Seshu m; DAUGHERTY, ROBERT E
Subject: [aai] [so] aai-common 1.2.0 depends on expired oparent snapshot

Hello AAI Team,

SO has a dependency on your aai-schema 1.2.0 release artifact, but recently all 
of our builds are failing due to this dependency.

It appears aai-common and by extension aai-schema release artifacts have a 
dependency on oparent 1.1.0-SNAPSHOT which no longer exists 
(https://nexus.onap.org/content/repositories/snapshots/org/onap/oparent/oparent/
 ):

Build failed to find artifact org.onap.oparent:oparent:pom:1.1.0-SNAPSHOT 
needed for sub-project org.onap.so:common:jar:1.2.0-SNAPSHOT: Failed to collect 
dependencies at org.onap.aai.aai-common:aai-schema:jar:1.2.0: Failed to read 
artifact descriptor for org.onap.aai.aai-common:aai-schema:jar:1.2.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.

See: 
https://nexus.onap.org/content/repositories/releases/org/onap/aai/aai-common/aai-common/1.2.0/aai-common-1.2.0.pom

All of our verify builds are failing due to this dependency. It seems the 
dependency should be on oparent 1.1.0 and not 1.1.0-SNAPSHOT.

I think we can work around temporarily by using aai-schema 1.2.1-SNAPSHOT which 
is based on oparent 1.1.0. However it would seem reasonable to fix this 
dependency issue on AAI released artifacts side.

Cheers,
Marcus Williams
IRC @ mgkwill
Network Software Engineer
Intel Corp. – Network Platforms Group

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

[onap-discuss] SO weekly meeting change as per DST

2018-03-12 Thread Seshu m

Dear Fellow SO ONAPers,

In due to the DST change in US and Europe, the SO weekly meeting tomorrow would 
be held @ Wed UTC 13:30 / China 21:30 / Eastern 09:30 / Pacific 06:30
one hour earlier in other parts (Non Daylight following nations).


Best regards
Seshu Kumar M
Huawei Technologies India Pvt, Ltd.


本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
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] TOSCA service instantiation fails

2018-03-06 Thread Seshu m

Hi Pavithra

Please share us the logs of SO and was the instance created before deleted 
before you re-tried the create service.


Best regards
Seshu Kumar M
Huawei Technologies India Pvt, Ltd.


本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
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 Pavithra R13
Sent: Wednesday, March 07, 2018 1:55 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] TOSCA service instantiation fails

Hi All

We have set up Kubernetes based ONAP and created  TOSCA based E2E service. We 
are able to instantiate the E2E service directly using SO API. But while 
instantiating the E2E service through UUI we are facing “Internal Server 
Error”. Could you please help in resolving the issue. Please find below 
screenshot for reference.

[cid:image001.jpg@01D3B629.98572A40]

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

[onap-discuss] ONAP Jira system is down

2018-02-06 Thread Seshu m

Dear LF

ONAP Jira is throwing a timeout error when tried to access any specific content.
Request to kindly look into the issue asap.


Best regards
Seshu Kumar M
Huawei Technologies India Pvt, Ltd.

本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
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] High number of old pending commits

2018-01-30 Thread Seshu m

Thanks Gildas,
Also, suggest and request the contributors to kindly add the reviewers while 
making any git contributions.
This would really help fasten the review process as sometimes committers might 
not be able to check specific project chekins.


Best regards
Seshu Kumar M
Huawei Technologies India Pvt, Ltd.

本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
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 Gildas Lanilis
Sent: Tuesday, January 30, 2018 1:40 AM
To: onap-rele...@lists.onap.org; onap-discuss@lists.onap.org
Subject: [onap-discuss] High number of old pending commits

Hi All,

As discussed during the PTL meeting this am, there is currently a high volume 
of commits that have been pending for months.
The list is available here.

I think that by respect to those who have made a contribution to the ONAP code, 
we should provide them some feedback, either by reviewing and commenting the 
work, abandon the work (It may very well not be useful anymore) or by merging 
the code into Master.
I understand there are some commits for which the discussion goes back and 
forth. That is a good sign of maturity, however this should not take months.

Thanks all for your support in spending a bit of time to review this list.

Thanks,
Gildas

[HuaweiLogowithName]
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] compile:so

2017-11-16 Thread Seshu m

Aijianwen

SO artifacts are now bumped to 1.1.1 version
As I see from the error the compilation is tsill trying to pick from the 1.1.0,
This is same with other artifacts of ither projects too.
You can clean up the repo and try to build again.

Best Regards,
Seshu
**
 This email 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 here 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 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*

From: onap-discuss-boun...@lists.onap.org [onap-discuss-boun...@lists.onap.org] 
on behalf of aijianwen [aijian...@huawei.com]
Sent: Friday, November 17, 2017 9:06 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] compile:so

Hi,team
Some error about so:
[INFO] so . SUCCESS [  2.215 s]
[INFO] MSO Common classes . SUCCESS [ 11.257 s]
[INFO] API Handler  SUCCESS [  0.429 s]
[INFO] mso-requests-db  SUCCESS [  2.395 s]
[INFO] mso-catalog-db . SUCCESS [  4.557 s]
[INFO] ECOMP MSO API Handler common ... SUCCESS [  3.011 s]
[INFO] MSO Status Control module .. SUCCESS [  2.413 s]
[INFO] mso-api-handler-infra .. SUCCESS [ 21.500 s]
[INFO] MSO Adapters ... SUCCESS [  0.407 s]
[INFO] mso-adapter-utils .. SUCCESS [01:19 min]
[INFO] mso-adapters-rest-interface  SUCCESS [  4.727 s]
[INFO] mso-network-adapter-async-client ... SUCCESS [  3.143 s]
[INFO] mso-network-adapter  SUCCESS [ 18.527 s]
[INFO] mso-sdnc-adapter ... SUCCESS [  4.297 s]
[INFO] mso-tenant-adapter . SUCCESS [  4.606 s]
[INFO] mso-vnf-adapter-async-client ... SUCCESS [  2.793 s]
[INFO] mso-vnf-adapter  SUCCESS [ 10.235 s]
[INFO] mso-requests-db-adapter  SUCCESS [  3.383 s]
[INFO] mso-catalog-db-adapter . SUCCESS [ 13.401 s]
[INFO] mso-workflow-message-adapter ... SUCCESS [  1.809 s]
[INFO] mso-vfc-adapter  SUCCESS [  4.835 s]
[INFO] asdc-controller  SUCCESS [  6.932 s]
[INFO] BPMN Subsystem . SUCCESS [  0.363 s]
[INFO] MSOCoreBPMN  SUCCESS [  9.368 s]
[INFO] MSO REST Client API  SUCCESS [  0.469 s]
[INFO] MSOCommonBPMN .. FAILURE [  9.802 s]
[INFO] MSOInfrastructureBPMN .. SKIPPED
[INFO] MSOCockpit . SKIPPED
[INFO] MSO Packages ... SKIPPED
[INFO] MsoDeliveries .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 03:48 min
[INFO] Finished at: 2017-11-17T08:52:39+08:00
[INFO] Final Memory: 144M/4059M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.6.1:compile (default-compile) 
on project MSOCommonBPMN: Compilation failure: Compilation failure:
[ERROR] 
/directory/var/jenkins/workspace/so-compile-1.1.0/bpmn/MSOCommonBPMN/src/main/java/org/openecomp/mso/client/aai/AAIRestClient.java:[26,32]
 package org.onap.aai.domain.yang does not exist
[ERROR] 
/directory/var/jenkins/workspace/so-compile-1.1.0/bpmn/MSOCommonBPMN/src/main/java/org/openecomp/mso/client/aai/AAIRestClient.java:[27,32]
 package org.onap.aai.domain.yang does not exist
[ERROR] 
/directory/var/jenkins/workspace/so-compile-1.1.0/bpmn/MSOCommonBPMN/src/main/java/org/openecomp/mso/client/aai/AAIRestClient.java:[28,32]
 package org.onap.aai.domain.yang does not exist
[ERROR] 
/directory/var/jenkins/workspace/so-compile-1.1.0/bpmn/MSOCommonBPMN/src/main/java/org/openecomp/mso/client/aai/AAIRestClient.java:[35,9]
 cannot find symbol
[ERROR]   symbol:   class Pservers
[ERROR]   location: interface org.openecomp.mso.client.aai.AAIRestClient
[ERROR]

Re: [onap-discuss] SDC sdk versions

2017-10-31 Thread Seshu m

Michael Lando,

Updated for the SO, we too are using the SNAPSHOT versions.
This is currently blocking the SO docker build. Raised a bug to track the 
issue, SDC-561.

Best Regards,
Seshu
**
 This email 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 here 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 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*

From: TIMONEY, DAN [dt5...@att.com]
Sent: Tuesday, October 31, 2017 9:26 PM
To: LANDO, MICHAEL; DAUGHERTY, ROBERT E; FORSYTH, JAMES; JI, LUSHENG; SONSINO, 
OFIR; MAHER, RANDA; Seshu m
Cc: LEFEVRE, CATHERINE; FREEMAN, BRIAN D; UNO, LARRY; 
onap-discuss@lists.onap.org
Subject: Re: SDC sdk versions

Michael,

I filled in the SDNC info below.  Note – we’re still using SNAPSHOT versions, 
so if there is a release version we can use instead, that would be great.

Thanks!
Dan

Dan Timoney
Principal Technical Staff Member
AT
Email : dtimo...@att.com<mailto:dtimo...@att.com>
Office : +1 (732) 420-3226
Mobile : +1 (201) 960-1211
200 S Laurel Ave, Rm E2-2A03
Middletown, NJ 08873

From: "LANDO, MICHAEL" <ml6...@intl.att.com>
Date: Tuesday, October 31, 2017 at 8:09 AM
To: "TIMONEY, DAN" <dt5...@att.com>, "DAUGHERTY, ROBERT E" <rd4...@att.com>, 
"FORSYTH, JAMES" <jf2...@att.com>, "JI, LUSHENG" <l...@research.att.com>, 
"SONSINO, OFIR" <os0...@intl.att.com>, "MAHER, RANDA" <rx1...@att.com>, Seshu m 
<seshu.kuma...@huawei.com>
Cc: "LEFEVRE, CATHERINE" <cl6...@intl.att.com>, "FREEMAN, BRIAN D" 
<bf1...@att.com>, "UNO, LARRY" <l...@research.att.com>, 
"onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: SDC sdk versions

Hi,
I am trying to validate what version of the SDC dependency you are using so 
that I will be able to validate they are available as releases in LF please 
reply with the version your application is using.

>From what I know

  org.openecomp.sdc.sdc-distribution-client
  sdc-distribution-client


Users
Component

version

SO

 1.1.32-SNAPSHOT

SDNC

 1.1.32-SNAPSHOT

AA



DCAE



APPC






  org.openecomp.sdc.sdc-tosca
  sdc-tosca


Users
Component

version

SO

 1.1.32-SNAPSHOT

SDNC

 1.1.34-SNAPSHOT

VID








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<mailto: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 Helpdesk #47177] SO build failing due to no appc client jars in the staging repo

2017-10-23 Thread Seshu m

Thanks for the support provided.


Best regards
Seshu Kumar M
Huawei Technologies India Pvt, Ltd.


本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
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!


-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Tuesday, October 24, 2017 7:47 AM
To: Seshu m
Cc: Yunxia Chen; cl6...@intl.att.com; Gildas Lanilis; 
onap-discuss@lists.onap.org; rd4...@att.com
Subject: [ONAP Helpdesk #47177] SO build failing due to no appc client jars in 
the staging repo

Closing this case now. 

These issues have been resolved and the jobs look stable

Thanks!
Jess

On Wed Oct 18 12:42:08 2017, jwagantall wrote:
> Dear Seshu,
> 
> We are investigating the cause of these problems. For now, It looks 
> like there are recent builds that are passing now due to a new appc 
> daily job run that just happened this morning.
> 
> Sorry for the inconvenience.
> 
> Will re-trigger the latest so builds to make sure we are ok now that 
> the appc binaries are back
> 
> Thanks!
> Jess
> 
> On Wed Oct 18 02:51:07 2017, seshu.kuma...@huawei.com wrote:
> > Dear LF
> >
> > We are facing SO build failures due to appc client jar missing in 
> > the nexus staging repo.
> >
> > [ERROR] Failed to execute goal on project MSOCommonBPMN: Could not 
> > resolve dependencies for project
> > org.openecomp.so:MSOCommonBPMN:war:1.1.0-SNAPSHOT: The following 
> > artifacts could not be resolved: org.openecomp.appc.client:client- 
> > kit:jar:1.1.0, org.openecomp.appc.client:client-lib:jar:1.1.0: Could 
> > not find artifact org.openecomp.appc.client:client-kit:jar:1.1.0 in 
> > staging https://nexus.onap.org/content/repositories/staging/
> >
> >
> > https://jenkins.onap.org/job/so-master-verify-profile-
> > java/479/console
> > https://jenkins.onap.org/job/so-master-verify-profile-
> > java/480/console
> >
> > I inspected the recent code merges made on and after 17 Oct and dint 
> > find any code merge that would ideally effect this.
> > Please help us resolve this issue as this asap as this is blocking 
> > the entire ONAP integration test progress.
> >
> > 
> > Best regards
> > Seshu Kumar M
> > Huawei Technologies India Pvt, Ltd.
> > 
> > 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
> > 止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
> > 的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
> > 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] pairwise testing between SO and MultiCloud

2017-10-23 Thread Seshu m

Hi Bin

We can start the activity and fix the issue as and when we get them, 
as we have a very short time for the final release.
Would appreciate if Ethyn could lead this activity as was discussed before and 
we would be glad to support him.


Best regards
Seshu Kumar M
Huawei Technologies India Pvt, Ltd.


本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
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!

-Original Message-
From: Yang, Bin [mailto:bin.y...@windriver.com] 
Sent: Saturday, October 21, 2017 7:53 AM
To: Seshu m
Cc: onap-discuss@lists.onap.org; Xinhui Li (lxin...@vmware.com); Ethan Lynn 
(ethanly...@vmware.com); Kang Xi; Yang Xu (Yang, Fixed Network); Yunxia Chen
Subject: pairwise testing between SO and MultiCloud

Hi Seshu,

This is Bin Yang from MultiCloud team. 
As agreed that SO will use multicloud to mediate the API calls to 
underlying VIM, we need conduct the pairwise testing between SO and Multicloud 
before RC1. 
Could you let me know what time is proper for you to have a meeting for 
setting up such testing environment?

Thanks.

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

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

[onap-discuss] SO build failing due to no appc client jars in the staging repo

2017-10-18 Thread Seshu m

Dear LF

We are facing SO build failures due to appc client jar missing in the nexus 
staging repo.

[ERROR] Failed to execute goal on project MSOCommonBPMN: Could not resolve 
dependencies for project org.openecomp.so:MSOCommonBPMN:war:1.1.0-SNAPSHOT: The 
following artifacts could not be resolved: 
org.openecomp.appc.client:client-kit:jar:1.1.0, 
org.openecomp.appc.client:client-lib:jar:1.1.0: Could not find artifact 
org.openecomp.appc.client:client-kit:jar:1.1.0 in staging
https://nexus.onap.org/content/repositories/staging/


https://jenkins.onap.org/job/so-master-verify-profile-java/479/console
https://jenkins.onap.org/job/so-master-verify-profile-java/480/console

I inspected the recent code merges made on and after 17 Oct and dint find any 
code merge that would ideally effect this.
Please help us resolve this issue as this asap as this is blocking the entire 
ONAP integration test progress.


Best regards
Seshu Kumar M
Huawei Technologies India Pvt, Ltd.

本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
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] Performance issues with Nexus3 ?

2017-09-19 Thread Seshu m

Hi LF, Randa,

We are facing the similar issues for the SO builds too,
Its taking 1 �C 1.5 hours for each build whereas the same in local servers 
completes in 3-4 mins.


Best regards
Seshu Kumar M
Huawei Technologies India Pvt, Ltd.

本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
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 MAHER, RANDA
Sent: Wednesday, September 20, 2017 2:38 AM
To: onap-helpd...@rt.linuxfoundation.org; onap-discuss@lists.onap.org
Cc: ANAPAN-LAVALLE, HECTOR A; HAY, AARON; BRADY, PATRICK D
Subject: [onap-discuss] Performance issues with Nexus3 ?
Importance: High

Hello LF, et al…

We are having issues with Nexus3 �C things that normally take less than 5 
minutes are taking more than 2 hours and still going…
I’m wondering if there is an issue with Nexus3 or if it’s something local to 
us….

Anyone else having similar experience. This is really hampering productivity.

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

Re: [onap-discuss] [ONAP Helpdesk #45504] Re:Issue in Jenkins job

2017-09-18 Thread Seshu m

+Onap discuss...

Thanks Jess, that would really help a lot of us currently struggling with the 
build failures.

Best regards
Seshu Kumar M
Huawei Technologies India Pvt, Ltd.


本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
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!

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Tuesday, September 19, 2017 8:22 AM
To: Seshu m
Cc: Gildas Lanilis
Subject: [ONAP Helpdesk #45504] Re:Issue in Jenkins job

Actually, 
I am working with my team to set up a better scheduling for these jobs since we 
are almost reaching  1K Jenkins jobs

Will see if our fix helps with these jobs suddenly failing. 

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

Re: [onap-discuss] [so] Meeting weekly update and Meeting notice

2017-09-18 Thread Seshu m

Hi Dewayne and Rob,

Please join the SO story status meeting for the sprint 3.

Time: Sep 18, 2017 6:30 PM Mumbai, Kolkata, New Delhi

Join from PC, Mac, Linux, iOS or Android: https://huawei.zoom.us/j/561855496



MOM of SO meeting on 13-09 and latest status:

•Multi Vim – cloud objects
 •(R1 scope) SO is the owner was decided who would update AAI – Gil has 
provided the details.
Daniel would provide python 
script over Heat Bridge. – Workaround provide R1 timeframe.
We need a make a story for this 
– Rob created a story to track
 •Check the seed code to see how its done now and if we could do it the 
same – John
No more required
•Stories and priority - Seshu, Rob and Dewayne – 6:00am PST tomorrow
 •Sprint 2 – closed on sept 16th
 •Sprint 3 – In progress

l  Introduction to the new code changes – Mike’s team to help with the details
l  CSIT testing and automation
p  Robot Framework is ready.
p  Test cases to be added for the Robot FW on VCPE and VoLTE
l  Coverage of code – 12.5% to reach at least 30%
p  Interface level testing for the UT
l  Sonar issues
p  Blockers and Critical to be handled
l  Docker 1.1.0 version and location would be under Ecomp in Nexus3
p  Rob to check the configuration with Mike for the OOM vs SO.
p  Jimmy from AAI compatibility.

Workflow training and introduction on the tools helpful for documentation – F2F 
France
Developer Guide helpful to users of the SO – in the wiki




Best regards
Seshu Kumar M
Huawei Technologies India Pvt, Ltd.

本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
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: Seshu m
Sent: Thursday, September 07, 2017 1:46 AM
To: onap-discuss@lists.onap.org; BULLARD, GIL; CHOMA, JOHN S; DAUGHERTY, ROBERT 
E; dewa...@cloudify.co; Chenchuanyu
Subject: [so] Meeting weekly update and Meeting notice


Topic: SO story status Meeting
Time: Sep 7, 2017 6:30 PM Mumbai, Kolkata, New Delhi

Join from PC, Mac, Linux, iOS or Android: https://huawei.zoom.us/j/561855496

Or iPhone one-tap :
US: +16465588656,,561855496#  or +16699006833,,561855496#
Or Telephone：
Dial(for higher quality, dial a number based on your current location)：
US: +1 646 558 8656  or +1 669 900 6833
Meeting ID: 561 855 496
International numbers available: 
https://huawei.zoom.us/zoomconference?m=qiYTzxiBet-02A7nGdmVdB0f7ODT_C-H





•Blockers M4 – Show stoppers
•VCPE workflows –
 •SO SDC Kangxi – 8:30 IST to continue
 •BRG is changed from pnf to allotted resource, as currently pnf is not 
supported.
•Seed 1710 code merge
 •7/09 EOD - Rob is working on this
 •Decompose generic workflow – No objection so far @ the moment,
 •To be assigned to someone to be done.
 •List the tasks which needs to done and prioritize – Rob
•Multi Vim – cloud objects
 •(R1 scope) SO is the owner was decided who would update AAI – Gil
 •Check the seed code to see how its done now and if we could do it the 
same - John

•Stories and priority - Seshu, Rob and Dewayne – 6:00am PST tomorrow
 •Sprint 2
 •Sprint 3


Best Regards,
Seshu
**
 This email 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 here 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 
email 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] [aai] [so] XML namespace changing in AAI on Monday

2017-09-11 Thread Seshu m

James,

Thanks for this, SO code is migrated to 1710 version , thanks to Rob’s effort.
Would it be possible for us to discuss on this in a call.


Best regards
Seshu Kumar M
Huawei Technologies India Pvt, Ltd.

本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
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: FORSYTH, JAMES [mailto:jf2...@att.com]
Sent: Saturday, September 09, 2017 4:20 AM
To: Seshu m; DAUGHERTY, ROBERT E
Cc: onap-discuss@lists.onap.org
Subject: [aai] [so] XML namespace changing in AAI on Monday

Rob and Seshu,

As discussed previously, AAI is changing the XML namespace from 
http://org.openecomp.aai.inventory/v11 to http://org.onap.aai.inventory/v11 - 
this change will happen Monday.  Please let me know if you need anything else 
from us.  Anyone else who uses the XML interface to AAI, please be aware that 
this change will happen Monday.

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

Re: [onap-discuss] [ONAP Helpdesk #45502] Issue in Jenkins job

2017-09-11 Thread Seshu m

Hi Jess


job id 
https://jenkins.onap.org/job/so-master-verify-csit-sanity-check/13/

I raised another issue for this, #45504
Perhaps you can close this as duplicate and investigate the other one.

Best regards
Seshu Kumar M
Huawei Technologies India Pvt, Ltd.


本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
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!

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Friday, September 08, 2017 1:15 AM
To: Seshu m
Cc: Gildas Lanilis
Subject: [ONAP Helpdesk #45502] Issue in Jenkins job

Dear Seshu, 

could you please share with me the issue's log? or maybe the failed job please?

Thanks!
Jess
___
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

2017-09-11 Thread Seshu m

Thanks Jess, merge done for SO.



Best regards
Seshu Kumar M
Huawei Technologies India Pvt, Ltd.

本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
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-release-boun...@lists.onap.org 
[mailto:onap-release-boun...@lists.onap.org] On Behalf Of Gildas Lanilis
Sent: Saturday, September 09, 2017 4:27 AM
To: onap-discuss@lists.onap.org; onap-rele...@lists.onap.org
Cc: Jessica Wagantall'
Subject: [Onap-release] 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 ☺…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

[onap-discuss] [so] Meeting weekly update and Meeting notice

2017-09-06 Thread Seshu m

Topic: SO story status Meeting
Time: Sep 7, 2017 6:30 PM Mumbai, Kolkata, New Delhi

Join from PC, Mac, Linux, iOS or Android: https://huawei.zoom.us/j/561855496

Or iPhone one-tap :
US: +16465588656,,561855496#  or +16699006833,,561855496#
Or Telephone：
Dial(for higher quality, dial a number based on your current location)：
US: +1 646 558 8656  or +1 669 900 6833
Meeting ID: 561 855 496
International numbers available: 
https://huawei.zoom.us/zoomconference?m=qiYTzxiBet-02A7nGdmVdB0f7ODT_C-H





•Blockers M4 – Show stoppers
•VCPE workflows –
 •SO SDC Kangxi – 8:30 IST to continue
 •BRG is changed from pnf to allotted resource, as currently pnf is not 
supported.
•Seed 1710 code merge
 •7/09 EOD - Rob is working on this
 •Decompose generic workflow – No objection so far @ the moment,
 •To be assigned to someone to be done.
 •List the tasks which needs to done and prioritize – Rob
•Multi Vim – cloud objects
 •(R1 scope) SO is the owner was decided who would update AAI – Gil
 •Check the seed code to see how its done now and if we could do it the 
same - John

•Stories and priority - Seshu, Rob and Dewayne – 6:00am PST tomorrow
 •Sprint 2
 •Sprint 3



Best Regards,
Seshu
**
 This email 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 here 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 
email 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] [multicloud][so] ask for plan/discussion on the integration test between SO and Multi VIM/Cloud

2017-09-04 Thread Seshu m

Hi Xinhui,



Glad we could help you in the past,

Currently SO code needs a migration to the  ATT MSO 1710 that's high priority 
task in progress,

we could plan the integration testing after that are in place.

Meanwhile you could mockup the interfaces and do a initial testing and keep 
them ready.



Best Regards,
Seshu
**
 This email 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 here 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 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*

From: Xinhui Li [lxin...@vmware.com]
Sent: Friday, September 01, 2017 11:17 PM
To: Seshu m
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss][multicloud][so] ask for plan/discussion on the 
integration test between SO and Multi VIM/Cloud

Sorry for my typo mistake at group email address

From: Xinhui Li <lxin...@vmware.com>
Date: Friday, 1 September 2017 at 10:44 PM
To: Seshu m <seshu.kuma...@huawei.com>
Cc: "onap-discuss-boun...@lists.onap.org" <onap-discuss-boun...@lists.onap.org>
Subject: [onap-discuss][multicloud][so] ask for plan/discussion on the 
integration test between SO and Multi VIM/Cloud

Hi Seshu,

Thanks for the SO team’s help in the past Sprint to settle down the API/use 
case with Multi VIM/Cloud team.

We have got our keystone proxy set up, uploaded related binary to Nexus3, and 
will provide document accordingly. I wonder when is convenient for SO team to 
discuss about test plan on the integration between SO and Multi VIM/Cloud. 
Ideally, we need to this iteratively before final end2end integration. At the 
same time, Multi VIM/Cloud team is working on UT and FT framework to cover API 
tests confirmed as https://wiki.onap.org/pages/viewpage.action?pageId=13599038

Thanks,

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

Re: [onap-discuss] [so][cli] REST API document

2017-08-23 Thread Seshu m

Hi Kanag

You can refer to the VID MSO  interfaces and the UUI interfaces listed in wiki.
These will be the same used by the external API FW too.

Best Regards,
Seshu
**
 This email 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 here 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 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*

From: onap-discuss-boun...@lists.onap.org [onap-discuss-boun...@lists.onap.org] 
on behalf of Kanagaraj Manickam [kanagaraj.manic...@huawei.com]
Sent: Wednesday, August 23, 2017 3:19 PM
To: 'onap-discuss@lists.onap.org'
Subject: [onap-discuss] [so][cli] REST API document

Hi Seshu,

Once SO REST API are finalized as part M3, kindly share the wiki link.
As discussed during last ARC meeting, CLI project will use it for implementing 
SO related commands

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

[onap-discuss] FW: SO weekly meeting

2017-08-16 Thread Seshu m

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:India Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0530
TZOFFSETTO:+0530
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0530
TZOFFSETTO:+0530
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Seshu m:MAILTO:seshu.kuma...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Xinhui Li:
 MAILTO:lxin...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Danny Lin:
 MAILTO:l...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Jinxin (Sa
 w):MAILTO:saw@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Zengjiangu
 o (OSS Design):MAILTO:zengjian...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Phi
 lip:MAILTO:aphi...@microsoft.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Yang, Bin":
 MAILTO:bin.y...@windriver.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=zhanganbin
 g...@chinamobile.com:MAILTO:zhanganb...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ethan Lynn
 :MAILTO:ethanly...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="CHOMA, JOH
 N S":MAILTO:jc1...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=DeWayne Fi
 lppi:MAILTO:dewa...@gigaspaces.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Byung-Woo 
 Jun:MAILTO:byung-woo@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=wangchengl
 i...@chinamobile.com:MAILTO:wangchen...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=zhongheliu
 @boco.com.cn:MAILTO:zhonghe...@boco.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=zhang.zhou
 1...@zte.com.cn:MAILTO:zhang.zh...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Chenchuany
 u:MAILTO:chenchua...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=yangyanyjy
 @chinamobile.com:MAILTO:yangyan...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="DAUGHERTY,
  ROBERT E":MAILTO:rd4...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lingli Den
 g:MAILTO:denglin...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=wu.liang@z
 te.com.cn:MAILTO:wu.li...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=yangyuanwe
 i...@boco.com.cn:MAILTO:yangyuan...@boco.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=denghui (L
 ):MAILTO:denghu...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Christophe
 r Donley (Chris):MAILTO:christopher.don...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=alex.vul@i
 ntel.com:MAILTO:alex@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Vijaykumar
  S:MAILTO:vijaykuma...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Praveen Kr
 ishnamurthy P:MAILTO:kprav...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="SOMASUNDAR
 AM, PRABHURAM":MAILTO:ps7...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="BULLARD, G
 IL":MAILTO:wb5...@att.com
DESCRIPTION;LANGUAGE=en-US:When: Occurs every Wednesday effective 8/16/2017
  from 7:00 PM to 8:00 PM (UTC+05:30) Chennai\, Kolkata\, Mumbai\, New Delh
 i.\n\nNote: The GMT offset above does not reflect daylight saving time adj
 ustments.\n\n*~*~*~*~*~*~*~*~*~*\n\n [so] Weekly Meeting\nhttps://zoom.us/
 j/309416964\n\nHi there\, ONAP Meeting 8 is inviting you to a scheduled Zo
 om meeting.\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/
 j/309416964\nOr\niPhone one-tap (US Toll): +14086380968\,\,309416964# or +
 16465588656\,\,309416964#\nOr\nTelephone: Dial: +1 408 638 0968 (US Toll) 
 or +1 646 558 8656 (US Toll) +1 855 880 1246 (US Toll Free) +1 877 369 092
 6 (US Toll Free)\nMeeting ID: 309 416 964\nInternational numbers available
 : https://zoom.us/zoomconference?m=30xXqK2sdCwPiwKQZLwqW5yEWuwQ7QHT\n\n
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=WE;WKST=SU
SUMMARY;LANGUAGE=en-US:FW: SO weekly meeting
DTSTART;TZID=India Standard Time:20170816T19
DTEND;TZID=India Standard Time:20170816T20
UID:04008200E00074C5B7101A82E008C07578307216D301000
 010005F0D2FDC0A38A040B56B13ACF1DF6DE1
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170816T040235Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:1737525217
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE

Re: [onap-discuss] {URGENT} RE: [so] Weekly Meeting

2017-08-10 Thread Seshu m

Thanks for the resolution provided.
Could you also provide the access rights to record the meetings.

Best Regards,
Seshu
**
 This email 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 here 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 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*

From: Kenny Paul [kp...@linuxfoundation.org]
Sent: Wednesday, August 09, 2017 11:29 PM
To: Seshu m
Cc: Xinhui Li; Danny Lin; Jinxin (Saw); Zengjianguo (OSS Design); Andrew 
Philip; Yang, Bin; zhanganb...@chinamobile.com; Ethan Lynn; CHOMA, JOHN S; 
DeWayne Filppi; Byung-Woo Jun; wangchen...@chinamobile.com; 
zhonghe...@boco.com.cn; zhang.zh...@zte.com.cn; Chenchuanyu; 
yangyan...@chinamobile.com; DAUGHERTY, ROBERT E; Lingli Deng; 
wu.li...@zte.com.cn; yangyuan...@boco.com.cn; BULLARD, GIL; denghui (L); 
Christopher Donley (Chris); alex@intel.com; Vijaykumar S; 
onap-discuss@lists.onap.org; Praveen Krishnamurthy P
Subject: Re: {URGENT} RE: [so] Weekly Meeting

Hi Seshu,

Again my apologies for the inconvenience. The LF has added an additional Zoom 
host account to accommodate moving your meeting from Mondays to Wednesdays and 
I have made the necessary changes.  Please verify that the information in G-cal 
and on your meeting's wiki page are both correct.  As mentioned in my other 
email, please let me know the ticket number that was issued for your change 
request so that I can do some RCA. I do not want something similar happening to 
someone else.

Thanks.

Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>
510.766.5945

On Aug 9, 2017, at 6:37 AM, Seshu m 
<seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>> wrote:

Hi Kenny

As is discussed over the call, we are getting an issue in initiating the call,
We are getting the error
"The HOST has another meeting in progress"


I had been sending remainders and requests to re-schedule the bridge to 
wednesday, but that dint happen.
Kindly help us resolve this issue at the earliest possible time.
We are waiting

Best Regards,
Seshu
**
 This email 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 here 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 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*
________
From: Seshu m [seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>]
Sent: Wednesday, August 09, 2017 7:35 PM
To: Xinhui Li; Danny Lin; Jinxin (Saw); Zengjianguo (OSS Design); Andrew 
Philip; Yang, Bin; 
zhanganb...@chinamobile.com<mailto:zhanganb...@chinamobile.com>; Ethan Lynn; 
CHOMA, JOHN S; DeWayne Filppi; Byung-Woo Jun; 
wangchen...@chinamobile.com<mailto:wangchen...@chinamobile.com>; 
zhonghe...@boco.com.cn<mailto:zhonghe...@boco.com.cn>; 
zhang.zh...@zte.com.cn<mailto:zhang.zh...@zte.com.cn>; Chenchuanyu; 
yangyan...@chinamobile.com<mailto:yangyan...@chinamobile.com>; DAUGHERTY, 
ROBERT E; Lingli Deng; wu.li...@zte.com.cn<mailto:wu.li...@zte.com.cn>; 
yangyuan...@boco.com.cn<mailto:yangyuan...@boco.com.cn>; BULLARD, GIL; denghui 
(L); Christopher Donley (Chris); alex@intel.com<mailto:alex@intel.com>; 
Vijaykumar S; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
Praveen Krishnamurthy P
Subject: [onap-discuss] [so] Weekly Meeting
When: Wednesday, August 09, 2017 9:30 PM-10:30 PM.
Where: Zoom

When: Wednesday, August 09, 2017 7:00 PM-8:00 PM (UTC+05:30) Chennai, Kolkata, 
Mumbai, New Delhi.
Where: Zoom

Note: The GMT offset above does not reflect daylight saving time adjustments.

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

[so] Weekly Meeting
https://zoom.us/j/309416964
Hi there,
ONAP Meeting 6 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/309416964 Or iPhone 
one-tap (US Toll): +14086380968,,309416964# or +16465588656,,309416964# Or 
Telephone: Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll

[onap-discuss] {URGENT} RE: [so] Weekly Meeting

2017-08-09 Thread Seshu m

Hi Kenny

As is discussed over the call, we are getting an issue in initiating the call,
We are getting the error
"The HOST has another meeting in progress"


I had been sending remainders and requests to re-schedule the bridge to 
wednesday, but that dint happen.
Kindly help us resolve this issue at the earliest possible time.
We are waiting

Best Regards,
Seshu
**
 This email 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 here 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 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*
____
From: Seshu m [seshu.kuma...@huawei.com]
Sent: Wednesday, August 09, 2017 7:35 PM
To: Xinhui Li; Danny Lin; Jinxin (Saw); Zengjianguo (OSS Design); Andrew 
Philip; Yang, Bin; zhanganb...@chinamobile.com; Ethan Lynn; CHOMA, JOHN S; 
DeWayne Filppi; Byung-Woo Jun; wangchen...@chinamobile.com; 
zhonghe...@boco.com.cn; zhang.zh...@zte.com.cn; Chenchuanyu; 
yangyan...@chinamobile.com; DAUGHERTY, ROBERT E; Lingli Deng; 
wu.li...@zte.com.cn; yangyuan...@boco.com.cn; BULLARD, GIL; denghui (L); 
Christopher Donley (Chris); alex@intel.com; Vijaykumar S; 
onap-discuss@lists.onap.org; Praveen Krishnamurthy P
Subject: [onap-discuss] [so] Weekly Meeting
When: Wednesday, August 09, 2017 9:30 PM-10:30 PM.
Where: Zoom

When: Wednesday, August 09, 2017 7:00 PM-8:00 PM (UTC+05:30) Chennai, Kolkata, 
Mumbai, New Delhi.
Where: Zoom

Note: The GMT offset above does not reflect daylight saving time adjustments.

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

[so] Weekly Meeting
https://zoom.us/j/309416964
Hi there,
ONAP Meeting 6 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/309416964 Or iPhone 
one-tap (US Toll): +14086380968,,309416964# or +16465588656,,309416964# 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: 309 416 964 
International numbers available: 
https://zoom.us/zoomconference?m=30xXqK2sdCwPiwKQZLwqW5yEWuwQ7QHT
1:30 PM - 2:30 PM UTC

Sorry about the timezone issue in the previous invite.

Best Regards,
Seshu
**
 This email 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 here 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 
email 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] [so] Weekly Meeting

2017-08-09 Thread Seshu m

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Australia Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Seshu m:MAILTO:seshu.kuma...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Xinhui Li:
 MAILTO:lxin...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Danny Lin:
 MAILTO:l...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Jinxin (Sa
 w):MAILTO:saw@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Zengjiangu
 o (OSS Design):MAILTO:zengjian...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Phi
 lip:MAILTO:aphi...@microsoft.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Yang, Bin":
 MAILTO:bin.y...@windriver.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=zhanganbin
 g...@chinamobile.com:MAILTO:zhanganb...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ethan Lynn
 :MAILTO:ethanly...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="CHOMA, JOH
 N S":MAILTO:jc1...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=DeWayne Fi
 lppi:MAILTO:dewa...@gigaspaces.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Byung-Woo 
 Jun:MAILTO:byung-woo@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=wangchengl
 i...@chinamobile.com:MAILTO:wangchen...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=zhongheliu
 @boco.com.cn:MAILTO:zhonghe...@boco.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=zhang.zhou
 1...@zte.com.cn:MAILTO:zhang.zh...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Chenchuany
 u:MAILTO:chenchua...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=yangyanyjy
 @chinamobile.com:MAILTO:yangyan...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="DAUGHERTY,
  ROBERT E":MAILTO:rd4...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lingli Den
 g:MAILTO:denglin...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=wu.liang@z
 te.com.cn:MAILTO:wu.li...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=yangyuanwe
 i...@boco.com.cn:MAILTO:yangyuan...@boco.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="BULLARD, G
 IL":MAILTO:wb5...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=denghui (L
 ):MAILTO:denghu...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Christophe
 r Donley (Chris):MAILTO:christopher.don...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=alex.vul@i
 ntel.com:MAILTO:alex@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Vijaykumar
  S:MAILTO:vijaykuma...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Praveen Kr
 ishnamurthy P:MAILTO:kprav...@huawei.com
DESCRIPTION;LANGUAGE=en-US:When: Wednesday\, August 09\, 2017 7:00 PM-8:00 
 PM (UTC+08:00) Perth.\nWhere: Zoom\n\nNote: The GMT offset above does not 
 reflect daylight saving time adjustments.\n\n*~*~*~*~*~*~*~*~*~*\n\n[so] W
 eekly Meeting\nhttps://zoom.us/j/309416964\nHi there\,\nONAP Meeting 6 is 
 inviting you to a scheduled Zoom meeting.\nJoin from PC\, Mac\, Linux\, iO
 S or Android: https://zoom.us/j/309416964 Or iPhone one-tap (US Toll): +14
 086380968\,\,309416964# or +16465588656\,\,309416964# 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: 309 416 964 Interna
 tional numbers available: https://zoom.us/zoomconference?m=30xXqK2sdCwPiwK
 QZLwqW5yEWuwQ7QHT\n1:30 PM - 2:30 PM\n\nBest Regards\,\nSeshu\n***
 **
 *\n This email and its attachments contain confidential information fr
 om HUAWEI\, which is intended only for the person or entity whose address 
 is listed above. Any use of the information contained here in any way (inc
 luding\, but not limited to\, total or partial disclosure\, reproduction\,
  or dissemination) by persons other than the intended recipient(s) is proh
 ibited. If you receive this email in error\, please notify the sender by p
 hone or email immediately and delete it!\n ***

[onap-discuss] [so] Weekly Meeting

2017-08-09 Thread Seshu m

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:India Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0530
TZOFFSETTO:+0530
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0530
TZOFFSETTO:+0530
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Seshu m:MAILTO:seshu.kuma...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Xinhui Li:
 MAILTO:lxin...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Danny Lin:
 MAILTO:l...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Jinxin (Sa
 w):MAILTO:saw@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Zengjiangu
 o (OSS Design):MAILTO:zengjian...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Phi
 lip:MAILTO:aphi...@microsoft.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Yang, Bin":
 MAILTO:bin.y...@windriver.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=zhanganbin
 g...@chinamobile.com:MAILTO:zhanganb...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ethan Lynn
 :MAILTO:ethanly...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="CHOMA, JOH
 N S":MAILTO:jc1...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=DeWayne Fi
 lppi:MAILTO:dewa...@gigaspaces.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Byung-Woo 
 Jun:MAILTO:byung-woo@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=wangchengl
 i...@chinamobile.com:MAILTO:wangchen...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=zhongheliu
 @boco.com.cn:MAILTO:zhonghe...@boco.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=zhang.zhou
 1...@zte.com.cn:MAILTO:zhang.zh...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Chenchuany
 u:MAILTO:chenchua...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=yangyanyjy
 @chinamobile.com:MAILTO:yangyan...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="DAUGHERTY,
  ROBERT E":MAILTO:rd4...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lingli Den
 g:MAILTO:denglin...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=wu.liang@z
 te.com.cn:MAILTO:wu.li...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=yangyuanwe
 i...@boco.com.cn:MAILTO:yangyuan...@boco.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="BULLARD, G
 IL":MAILTO:wb5...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=denghui (L
 ):MAILTO:denghu...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Christophe
 r Donley (Chris):MAILTO:christopher.don...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=alex.vul@i
 ntel.com:MAILTO:alex@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Vijaykumar
  S:MAILTO:vijaykuma...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Praveen Kr
 ishnamurthy P:MAILTO:kprav...@huawei.com
DESCRIPTION;LANGUAGE=en-US:When: Wednesday\, August 09\, 2017 7:00 PM-8:00 
 PM (UTC+05:30) Chennai\, Kolkata\, Mumbai\, New Delhi.\nWhere: Zoom\n\nNot
 e: The GMT offset above does not reflect daylight saving time adjustments.
 \n\n*~*~*~*~*~*~*~*~*~*\n\n[so] Weekly Meeting\nhttps://zoom.us/j/30941696
 4\nHi there\,\nONAP Meeting 6 is inviting you to a scheduled Zoom meeting.
 \nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/309416964
  Or iPhone one-tap (US Toll): +14086380968\,\,309416964# or +16465588656\,
 \,309416964# Or Telephone: Dial: +1 408 638 0968 (US Toll) or +1 646 558 8
 656 (US Toll) +1 855 880 1246 (US Toll Free) +1 877 369 0926 (US Toll Free
 ) Meeting ID: 309 416 964 International numbers available: https://zoom.us
 /zoomconference?m=30xXqK2sdCwPiwKQZLwqW5yEWuwQ7QHT\n1:30 PM - 2:30 PM UTC\
 n\nSorry about the timezone issue in the previous invite.\n\nBest Regards\
 ,\nSeshu\n
 **\n This email and its attachments contain confid
 ential information from HUAWEI\, which is intended only for the person or 
 entity whose address is listed above. Any use of the information contained
  here in any way (including\, but not limited to\, total or partial disclo
 sure\, reproduction\, or dissemination) by persons other than the intended
  recipient(s) is prohibited. If you receive this email in error\, please n
 otify the sender by phone or email immediately and delete

[onap-discuss] [so] Weekly Meeting

2017-08-09 Thread Seshu m


[so] Weekly Meeting
https://zoom.us/j/309416964
Hi there,
ONAP Meeting 6 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/309416964 Or iPhone 
one-tap (US Toll): +14086380968,,309416964# or +16465588656,,309416964# 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: 309 416 964 
International numbers available: 
https://zoom.us/zoomconference?m=30xXqK2sdCwPiwKQZLwqW5yEWuwQ7QHT
2:00 PM - 3:00 PM

Best Regards,
Seshu
**
 This email 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 here 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 
email 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] [so] Need re-schedule the SO weekly meeting

2017-08-07 Thread Seshu m

Hi Kenny



This issue is still open and is creating confusion amongst the SO meeting 
participants.

I have also logged the request in TSC meeting page too.

Request to kindly handle this at the earliest,





Best Regards,
Seshu
**
 This email 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 here 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 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*

From: Kenny Paul [kp...@linuxfoundation.org]
Sent: Saturday, July 29, 2017 12:42 AM
To: Seshu m
Cc: onap-discuss@lists.onap.org
Subject: Re: [so] Need re-schedule the SO weekly meeting

Hi Seshu,
I understand completely. Given the number of meetings already scheduled on 
Wednesdays I may need to juggle some of the other bridge numbers around, but it 
is doable.
If you can, please submit this request via the meeting page and just note that 
it is a schedule change in the message.
That will ensure that your request doesn’t fall through the cracks.

Thanks!


Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>
510.766.5945

On Jul 27, 2017, at 10:49 PM, Seshu m 
<seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>> wrote:

Dear Kenny



To avoid the conflict with the Usecase committee Meeting, SO team has decided 
to have the weekly meetings scheduled at 6:30 am PST every Wednesday.
Request to kindly change the bridge, also request to provide the recording 
access for the same.



Best Regards,
Seshu
**
 This email 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 here 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 
email 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] Topic: SO Weekly Meeting schedule

2017-08-02 Thread Seshu m

Gentle Remainder...



Best Regards,
Seshu
**
 This email 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 here 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 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*

From: Seshu m
Sent: Tuesday, August 01, 2017 4:19 PM
To: onap-discuss@lists.onap.org
Subject: Topic: SO Weekly Meeting schedule


Hi ,



We are still waiting for the LF to switch the bridge of SO.

Meanwhile, please find the details of the SO weekly meeting



Timings Wednesday : UTC 1:30 pm

China Time 9:30 pm

Pacific time 6:30 am





Seshu Kumar M is inviting you to a scheduled Zoom meeting.

Topic: SO Weekly Meeting schedule
Time: this is a recurring meeting Meet anytime

Join from PC, Mac, Linux, iOS or Android: https://huawei.zoom.us/j/780675195

Or iPhone one-tap (US Toll):  +16465588656,,780675195# or 
+14086380968,,780675195#

Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
Meeting ID: 780 675 195
International numbers available: 
https://huawei.zoom.us/zoomconference?m=vppjsEx1yN9cPiy_ctKyYvAirGwfo1Ty

Or an H.323/SIP room system:
H.323:
162.255.37.11 (US West)
162.255.36.11 (US East)
221.122.88.195 (China)
115.114.131.7 (India)
213.19.144.110 (EMEA)
202.177.207.158 (Australia)
209.9.211.110 (Hong Kong)
64.211.144.160 (Brazil)
Meeting ID: 780 675 195

SIP: 780675...@zoomcrc.com<mailto:780675...@zoomcrc.com>





Best Regards,
Seshu
**
 This email 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 here 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 
email 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] Topic: SO Weekly Meeting schedule

2017-08-01 Thread Seshu m

Hi ,



We are still waiting for the LF to switch the bridge of SO.

Meanwhile, please find the details of the SO weekly meeting



Timings Wednesday : UTC 1:30 pm

China Time 9:30 pm

Pacific time 6:30 am





Seshu Kumar M is inviting you to a scheduled Zoom meeting.

Topic: SO Weekly Meeting schedule
Time: this is a recurring meeting Meet anytime

Join from PC, Mac, Linux, iOS or Android: https://huawei.zoom.us/j/780675195

Or iPhone one-tap (US Toll):  +16465588656,,780675195# or 
+14086380968,,780675195#

Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
Meeting ID: 780 675 195
International numbers available: 
https://huawei.zoom.us/zoomconference?m=vppjsEx1yN9cPiy_ctKyYvAirGwfo1Ty

Or an H.323/SIP room system:
H.323:
162.255.37.11 (US West)
162.255.36.11 (US East)
221.122.88.195 (China)
115.114.131.7 (India)
213.19.144.110 (EMEA)
202.177.207.158 (Australia)
209.9.211.110 (Hong Kong)
64.211.144.160 (Brazil)
Meeting ID: 780 675 195

SIP: 780675...@zoomcrc.com





Best Regards,
Seshu
**
 This email 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 here 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 
email 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] [so] Need re-schedule the SO weekly meeting

2017-07-27 Thread Seshu m

Dear Kenny



To avoid the conflict with the Usecase committee Meeting, SO team has decided 
to have the weekly meetings scheduled at 6:30 am PST every Wednesday.

Request to kindly change the bridge, also request to provide the recording 
access for the same.



Best Regards,
Seshu
**
 This email 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 here 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 
email 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] [modeling] Please vote for chairperson of Modeling Subcommittee

2017-07-06 Thread Seshu m

+1



Best Regards,
Seshu
**
 This email 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 here 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 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*

From: onap-discuss-boun...@lists.onap.org [onap-discuss-boun...@lists.onap.org] 
on behalf of denghui (L) [denghu...@huawei.com]
Sent: Friday, July 07, 2017 11:56 AM
To: onap-...@lists.onap.org; onap-discuss@lists.onap.org
Subject: [onap-discuss] [modeling] Please vote for chairperson of Modeling 
Subcommittee

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] The Polling Result.RE: SO project PTL Election

2017-06-28 Thread Seshu m

Dear All,

Thanks all for the confidence and trust shown in me for the position,

I will setup a weekly meeting schedule for the SO project with LF and publish 
it sooner.

My fellow SO committers and contributorsm, require all your suggestions and 
support to make the project a success.

Best Regards,
Seshu
**
 This email 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 here 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 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*

From: onap-discuss-boun...@lists.onap.org [onap-discuss-boun...@lists.onap.org] 
on behalf of Jinxin (Saw) [saw@huawei.com]
Sent: Thursday, June 29, 2017 12:07 PM
To: onap-discuss@lists.onap.org; onap-...@lists.onap.org
Cc: Zhoujun (John, IES SOURCE)
Subject: [onap-discuss] The Polling Result.RE: SO project PTL Election


Dear SO project committers:
Thanks for voting. The poll was closed on 2017/06/29 12:00:00 UTC+8.
Seshu Kumar M has been voted as PTL of SO project. Congratulations.
Details of voting result can be seen at
http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_92fafe458c577560

Best wishes
Jinxin

***
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**

***
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: Jinxin (Saw)
Sent: 2017年6月27日 12:00
To: onap-discuss@lists.onap.org; 'onap-...@lists.onap.org' 

Cc: Zhoujun (John, IES SOURCE) 
Subject: [onap-discuss] SO project PTL Election

Dear SO project committers：

I have setup the polling for ONAP SO PTL election, and kindly complete the 
voting before 2017/06/29 12:00:00 UTC+8

Thank you.

Best wishes
Jinxin

***
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**

***
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] Service Orchestrator PTL nominations : selfnomination

2017-06-20 Thread Seshu m


All,

I'd like to self-nominate for PTL role of the ONAP Service Orchestrator project.

I have 13+ years of industry experience and have involved myself in different 
roles as a individual contributor, development lead, version manager,  system 
architect and analyst,
having worked on Network Management system applications, OSS applications and 
workflow engines which includes open source projects.
I had been co-founder and core committer for the OPEN-O GSO and OPEN-O Client 
projects and sub project PTL for OPEN-O SDNO, while having proposed various 
solutions & enhancements in these projects have also the highest code 
contribution and commits for OPEN-O Mercury release. I have a good 
understanding of the orchestration engines with good knowledge on BPMN and 
TOSCA.
I also have hands-on experience both in leading projects using different 
methodologies (scrum/agile/XP/TDD) and in development of many Java/JEE based 
projects including the open source ones as apart of my assignments for Alcatel 
and Huawei.

Give an opportunity, it would be my pleasure to serve the role and provide my 
best for the success of the SO and all its dependent projects.



Seshu Kumar M
System Architect
Huawei Technologies India Pvt, Ltd.

本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
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] Service Orchestrator PTL nominations : selfnomination

2017-06-20 Thread Seshu m

All,

I'd like to self-nominate for PTL role of the ONAP Service Orchestrator project.

I have 13+ years of industry experience and have involved myself in different 
roles as a individual contributor, development lead, version manager,  system 
architect and analyst,
having worked on Network Management system applications, OSS applications and 
workflow engines which includes open source projects.
I had been co-founder and core committer for the OPEN-O GSO and OPEN-O Client 
projects and sub project PTL for OPEN-O SDNO, while having proposed various 
solutions & enhancements in these projects have also the highest code 
contribution and commits for OPEN-O Mercury release. I have a good 
understanding of the orchestration engines with good knowledge on BPMN and 
TOSCA.
I also have hands-on experience both in leading projects using different 
methodologies (scrum/agile/XP/TDD) and in development of many Java/JEE based 
projects including the open source ones as apart of my assignments for Alcatel 
and Huawei.

Give an opportunity, it would be my pleasure to serve the role and provide my 
best for the success of the SO and all its dependent projects.



Seshu Kumar M
System Architect
Huawei Technologies India Pvt, Ltd.

本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
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

44 matches

Mail list logo