Re: [onap-discuss] Rancher Based Deployment - 404 Error

[Pulkit Walia]

Thank You Victor.
I will refer to these links as well.

Regards,
Pulkit

From: Morales, Victor [mailto:victor.mora...@intel.com]
Sent: Thursday, June 7, 2018 6:58 AM
To: Pulkit Walia ; Roger Maitland 
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Rancher Based Deployment - 404 Error

Hey Pulkit,

I tried to collect and put all the instructions for installing Rancher here 
[1]. The Devtool supports two methods to deploy Kubernetes (kubespray and 
rancher) for OOM and the deployment_tool variable [2] defines the method to be 
used.  There is more documentation here [3]

Regards,
Victor Morales

[1] 
https://git.onap.org/integration/devtool/tree/lib/_installers#n312
[2] 
https://git.onap.org/integration/devtool/tree/lib/oom#n6
[3] 
http://onap.readthedocs.io/en/latest/submodules/integration/devtool.git/docs/source/


From: 
mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of Pulkit Walia mailto:pwa...@vmware.com>>
Date: Wednesday, June 6, 2018 at 10:55 AM
To: Roger Maitland mailto:roger.maitl...@amdocs.com>>
Cc: "onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] Rancher Based Deployment - 404 Error

Thanks Roger!
I was exactly looking for this link, will surely refer to it now.

Regards,
Pulkit

On 06-Jun-2018 11:21 PM, Roger Maitland 
mailto:roger.maitl...@amdocs.com>> wrote:
Rancher installation of K8s is still the recommended method.  You’ll find the 
link to the documentation under the Cloud Setup Guide but here is the direct 
link: 
http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_setup_kubernetes_rancher.html

Cheers,
Roger

From: Pulkit Walia mailto:pwa...@vmware.com>>
Date: Wednesday, June 6, 2018 at 1:49 PM
To: Roger Maitland mailto:roger.maitl...@amdocs.com>>
Cc: "onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] Rancher Based Deployment - 404 Error

Thank You Roger.

I'll surely refer to these links. I thought that Rancher based installation 
still existed for Beijing Release.

Regards,
Pulkit

On 06-Jun-2018 11:11 PM, Roger Maitland 
mailto:roger.maitl...@amdocs.com>> wrote:
The processes have changed for Beijing.  You can find the official 
documentation for installation and operation of ONAP with OOM 
here:http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_project_description.html

The OOM documentation is broken into four different areas each targeted at a 
different user:

  *   OOM Quick Start 
Guide
 - deploy ONAP on an existing cloud
  *   OOM User 
Guide
 - a guide 

Re: [onap-discuss] Rancher Based Deployment - 404 Error

[Morales, Victor]

Hey Pulkit,

I tried to collect and put all the instructions for installing Rancher here 
[1]. The Devtool supports two methods to deploy Kubernetes (kubespray and 
rancher) for OOM and the deployment_tool variable [2] defines the method to be 
used.  There is more documentation here [3]

Regards,
Victor Morales

[1] https://git.onap.org/integration/devtool/tree/lib/_installers#n312
[2] https://git.onap.org/integration/devtool/tree/lib/oom#n6
[3] 
http://onap.readthedocs.io/en/latest/submodules/integration/devtool.git/docs/source/


From:  on behalf of Pulkit Walia 

Date: Wednesday, June 6, 2018 at 10:55 AM
To: Roger Maitland 
Cc: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] Rancher Based Deployment - 404 Error

Thanks Roger!
I was exactly looking for this link, will surely refer to it now.

Regards,
Pulkit

On 06-Jun-2018 11:21 PM, Roger Maitland  wrote:
Rancher installation of K8s is still the recommended method.  You’ll find the 
link to the documentation under the Cloud Setup Guide but here is the direct 
link: 
http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_setup_kubernetes_rancher.html

Cheers,
Roger

From: Pulkit Walia 
Date: Wednesday, June 6, 2018 at 1:49 PM
To: Roger Maitland 
Cc: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] Rancher Based Deployment - 404 Error

Thank You Roger.

I'll surely refer to these links. I thought that Rancher based installation 
still existed for Beijing Release.

Regards,
Pulkit

On 06-Jun-2018 11:11 PM, Roger Maitland  wrote:
The processes have changed for Beijing.  You can find the official 
documentation for installation and operation of ONAP with OOM 
here:http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_project_description.html

The OOM documentation is broken into four different areas each targeted at a 
different user:

  *   OOM Quick Start 
Guide
 - deploy ONAP on an existing cloud
  *   OOM User 
Guide
 - a guide for operators of an ONAP instance
  *   OOM Developer 
Guide
 - a guide for developers of OOM and ONAP
  *   OOM Cloud Setup 
Guide
 - a guide for those setting up cloud environments that ONAP will use

Hopefully it will go smoothly for you.

Cheers,
Roger

From: Pulkit Walia 
Date: Wednesday, June 6, 2018 at 1:36 PM
To: Roger Maitland 
Cc: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] Rancher Based Deployment - 404 Error

Hi Roger,

I am trying to install Beijing Release.

Regards,
Pulkit

On 06-Jun-2018 10:48 PM, Roger Maitland  wrote:
Which version of ONAP are you trying to install?

Cheers,
Roger

From:  on behalf of Pulkit Walia 

Date: Wednesday, June 6, 2018 at 7:18 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] Rancher Based Deployment - 404 Error

Hi All,

I am trying to deploy ONAP on Kubernetes using Rancher.
In the following link --> 

[onap-discuss] [sdnc] Master branch ready for Casablanca development

[TIMONEY, DAN]

SDNC team,

I wanted to let the team know that a separate branch has been created in ONAP 
Gerrit for the SDNC  northbound and oam repos (branch named “beijing”).  I’ve 
updated the master branch so that it is ready for Casablanca development to 
begin.

For Casablanca, the initial version we will use for those repositories is 
1.4.0-SNAPSHOT.

Dan

Dan Timoney
Principal Technical Staff Member
AT
Email : dtimo...@att.com
Office : +1 (732) 420-3226
Mobile : +1 (201) 960-1211
200 S Laurel Ave, Rm E2-2A03
Middletown, NJ 08873
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Rancher Based Deployment - 404 Error

[Pulkit Walia]

Thanks Roger!
I was exactly looking for this link, will surely refer to it now.

Regards,
Pulkit

On 06-Jun-2018 11:21 PM, Roger Maitland  wrote:
Rancher installation of K8s is still the recommended method.  You’ll find the 
link to the documentation under the Cloud Setup Guide but here is the direct 
link: 
http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_setup_kubernetes_rancher.html

Cheers,
Roger

From: Pulkit Walia 
Date: Wednesday, June 6, 2018 at 1:49 PM
To: Roger Maitland 
Cc: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] Rancher Based Deployment - 404 Error

Thank You Roger.

I'll surely refer to these links. I thought that Rancher based installation 
still existed for Beijing Release.

Regards,
Pulkit

On 06-Jun-2018 11:11 PM, Roger Maitland  wrote:
The processes have changed for Beijing.  You can find the official 
documentation for installation and operation of ONAP with OOM 
here:http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_project_description.html

The OOM documentation is broken into four different areas each targeted at a 
different user:

  *   OOM Quick Start 
Guide
 - deploy ONAP on an existing cloud
  *   OOM User 
Guide
 - a guide for operators of an ONAP instance
  *   OOM Developer 
Guide
 - a guide for developers of OOM and ONAP
  *   OOM Cloud Setup 
Guide
 - a guide for those setting up cloud environments that ONAP will use

Hopefully it will go smoothly for you.

Cheers,
Roger

From: Pulkit Walia 
Date: Wednesday, June 6, 2018 at 1:36 PM
To: Roger Maitland 
Cc: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] Rancher Based Deployment - 404 Error

Hi Roger,

I am trying to install Beijing Release.

Regards,
Pulkit

On 06-Jun-2018 10:48 PM, Roger Maitland  wrote:
Which version of ONAP are you trying to install?

Cheers,
Roger

From:  on behalf of Pulkit Walia 

Date: Wednesday, June 6, 2018 at 7:18 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] Rancher Based Deployment - 404 Error

Hi All,

I am trying to deploy ONAP on Kubernetes using Rancher.
In the following link --> 
https://wiki.onap.org/display/DW/ONAP+on+Kubernetes+on+Rancher

I am unable to run the following commands, since the files are unavailable and 
it gives a 404 error for the same:

wget 

Re: [onap-discuss] Rancher Based Deployment - 404 Error

[Pulkit Walia]

Thank You Roger.

I'll surely refer to these links. I thought that Rancher based installation 
still existed for Beijing Release.

Regards,
Pulkit

On 06-Jun-2018 11:11 PM, Roger Maitland  wrote:
The processes have changed for Beijing.  You can find the official 
documentation for installation and operation of ONAP with OOM 
here:http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_project_description.html

The OOM documentation is broken into four different areas each targeted at a 
different user:

  *   OOM Quick Start 
Guide
 - deploy ONAP on an existing cloud
  *   OOM User 
Guide
 - a guide for operators of an ONAP instance
  *   OOM Developer 
Guide
 - a guide for developers of OOM and ONAP
  *   OOM Cloud Setup 
Guide
 - a guide for those setting up cloud environments that ONAP will use

Hopefully it will go smoothly for you.

Cheers,
Roger

From: Pulkit Walia 
Date: Wednesday, June 6, 2018 at 1:36 PM
To: Roger Maitland 
Cc: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] Rancher Based Deployment - 404 Error

Hi Roger,

I am trying to install Beijing Release.

Regards,
Pulkit

On 06-Jun-2018 10:48 PM, Roger Maitland  wrote:
Which version of ONAP are you trying to install?

Cheers,
Roger

From:  on behalf of Pulkit Walia 

Date: Wednesday, June 6, 2018 at 7:18 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] Rancher Based Deployment - 404 Error

Hi All,

I am trying to deploy ONAP on Kubernetes using Rancher.
In the following link --> 
https://wiki.onap.org/display/DW/ONAP+on+Kubernetes+on+Rancher

I am unable to run the following commands, since the files are unavailable and 
it gives a 404 error for the same:

wget 
https://jira.onap.org/secure/attachment/ID/aaiapisimpledemoopenecomporg.cer
wget 
https://jira.onap.org/secure/attachment/1ID/onap-parameters.yaml
wget 
https://jira.onap.org/secure/attachment/ID/aai-cloud-region-put.json

It will be helpful for me if anyone could send me 

Re: [onap-discuss] Rancher Based Deployment - 404 Error

[Roger Maitland]

The processes have changed for Beijing.  You can find the official 
documentation for installation and operation of ONAP with OOM 
here:http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_project_description.html

The OOM documentation is broken into four different areas each targeted at a 
different user:

  *   OOM Quick Start 
Guide
 - deploy ONAP on an existing cloud
  *   OOM User 
Guide
 - a guide for operators of an ONAP instance
  *   OOM Developer 
Guide
 - a guide for developers of OOM and ONAP
  *   OOM Cloud Setup 
Guide
 - a guide for those setting up cloud environments that ONAP will use

Hopefully it will go smoothly for you.

Cheers,
Roger

From: Pulkit Walia 
Date: Wednesday, June 6, 2018 at 1:36 PM
To: Roger Maitland 
Cc: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] Rancher Based Deployment - 404 Error

Hi Roger,

I am trying to install Beijing Release.

Regards,
Pulkit

On 06-Jun-2018 10:48 PM, Roger Maitland  wrote:
Which version of ONAP are you trying to install?

Cheers,
Roger

From:  on behalf of Pulkit Walia 

Date: Wednesday, June 6, 2018 at 7:18 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] Rancher Based Deployment - 404 Error

Hi All,

I am trying to deploy ONAP on Kubernetes using Rancher.
In the following link --> 
https://wiki.onap.org/display/DW/ONAP+on+Kubernetes+on+Rancher

I am unable to run the following commands, since the files are unavailable and 
it gives a 404 error for the same:

wget 
https://jira.onap.org/secure/attachment/ID/aaiapisimpledemoopenecomporg.cer
wget 
https://jira.onap.org/secure/attachment/1ID/onap-parameters.yaml
wget 
https://jira.onap.org/secure/attachment/ID/aai-cloud-region-put.json

It will be helpful for me if anyone could send me the active links for the 
following files.

Regards,
Pulkit
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

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

Re: [onap-discuss] Rancher Based Deployment - 404 Error

[Pulkit Walia]

Hi Roger,

I am trying to install Beijing Release.

Regards,
Pulkit

On 06-Jun-2018 10:48 PM, Roger Maitland  wrote:
Which version of ONAP are you trying to install?

Cheers,
Roger

From:  on behalf of Pulkit Walia 

Date: Wednesday, June 6, 2018 at 7:18 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] Rancher Based Deployment - 404 Error

Hi All,

I am trying to deploy ONAP on Kubernetes using Rancher.
In the following link --> 
https://wiki.onap.org/display/DW/ONAP+on+Kubernetes+on+Rancher

I am unable to run the following commands, since the files are unavailable and 
it gives a 404 error for the same:

wget 
https://jira.onap.org/secure/attachment/ID/aaiapisimpledemoopenecomporg.cer
wget 
https://jira.onap.org/secure/attachment/1ID/onap-parameters.yaml
wget 
https://jira.onap.org/secure/attachment/ID/aai-cloud-region-put.json

It will be helpful for me if anyone could send me the active links for the 
following files.

Regards,
Pulkit
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Install ONAP Beijing Release

[Roger Maitland]

You can find the official documentation for installation and operation of ONAP 
with OOM here: 
http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_project_description.html

The OOM documentation is broken into four different areas each targeted at a 
different user:

  *   OOM Quick Start 
Guide
 - deploy ONAP on an existing cloud
  *   OOM User 
Guide
 - a guide for operators of an ONAP instance
  *   OOM Developer 
Guide
 - a guide for developers of OOM and ONAP
  *   OOM Cloud Setup 
Guide
 - a guide for those setting up cloud environments that ONAP will use

The use of the ‘cd.sh’ script is not part of these instructions.

Cheers,
Roger

From:  on behalf of Borislav Glozman 

Date: Wednesday, June 6, 2018 at 11:04 AM
To: Soumyarup Paul , 
"'onap-discuss@lists.onap.org'" 
Cc: Syed Atif Husain , Gopal Sabhadiya 

Subject: Re: [onap-discuss] Install ONAP Beijing Release

Looks like something happened to helm repo and it is not running on your host.
Please run ‘nohup helm serve &’ and retry.

Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726
[amdocs-a]
Amdocs a Platinum member of 
ONAP

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Soumyarup Paul
Sent: Wednesday, June 6, 2018 1:47 PM
To: 'onap-discuss@lists.onap.org' 
Cc: Syed Atif Husain ; Gopal Sabhadiya 

Subject: [onap-discuss] Install ONAP Beijing Release

Hi All,

I am facing a few issues while installing the Beijing release.

  1.  In the cd.sh script, should I uncomment this move file code
 if [ "$BRANCH" == "master" ]; then

echo "moving values.yaml to oom/kubernetes/"

 #sudo cp values.yaml oom/kubernetes/onap



If so, what is the encryption method used for password which I would 
need to provide here –

openStackEncryptedPasswordHere: "c124921a3a0efbe579782cde8227681e"



2.  If I try to install using the default values then I get the following error 
–

List of ONAP Modules - look for terminating pods

NAMESPACE NAME   READY STATUS
RESTARTS   AGE   IP  NODE

kube-system   heapster-76b8cd7b5-dl28v   1/1   Running   0  
7d10.42.34.140
blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net

kube-system   kube-dns-5d7b4487c9-6d6m2  3/3   Running   0  
7d10.42.207.251   
blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net

kube-system   kubernetes-dashboard-f9577fffd-k5snh   1/1   Running   0  
7d10.42.149.137   
blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net

kube-system   monitoring-grafana-997796fcf-qdps2 1/1   Running   0  
7d10.42.132.98
blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net

kube-system   monitoring-influxdb-56fdcd96b-xctvq1/1   Running   0  
7d10.42.208.55
blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net

kube-system   tiller-deploy-54bcc55dd5-scrbq 1/1   Running   0  
7d10.42.61.176
blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net

 deleting /dockerdata-nfs

chmod: cannot access '/dockerdata-nfs/onap': No such file or directory

chmod: cannot access '/dockerdata-nfs/dev': No such file or directory

pull new oom

Cloning into 'oom'...

remote: Total 16470 (delta 0), reused 16470 (delta 0)

Receiving objects: 100% (16470/16470), 24.04 MiB | 14.89 MiB/s, done.

Resolving deltas: 100% (8252/8252), done.

Checking connectivity... done.

moving values.yaml to oom/kubernetes/

start onap pods



[common]

make[1]: Entering directory '/root/oom/kubernetes'

make[2]: Entering directory '/root/oom/kubernetes/common'



[common]

make[3]: Entering directory '/root/oom/kubernetes/common'

==> Linting common

[INFO] Chart.yaml: icon is recommended



1 chart(s) linted, no failures

Successfully packaged chart and saved it to: 
/root/oom/kubernetes/dist/packages/common-2.0.0.tgz

make[3]: Leaving directory '/root/oom/kubernetes/common'



[mariadb-galera]

make[3]: Entering directory '/root/oom/kubernetes/common'

Hang tight while we grab the latest from your chart repositories...

...Unable to get an update from the "local" chart repository 
(http://127.0.0.1:8879/charts):

Get http://127.0.0.1:8879/charts/index.yaml: dial tcp 127.0.0.1:8879: 
getsockopt: connection refused

...Successfully got an update from the 

Re: [onap-discuss] Rancher Based Deployment - 404 Error

[Roger Maitland]

Which version of ONAP are you trying to install?

Cheers,
Roger

From:  on behalf of Pulkit Walia 

Date: Wednesday, June 6, 2018 at 7:18 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] Rancher Based Deployment - 404 Error

Hi All,

I am trying to deploy ONAP on Kubernetes using Rancher.
In the following link --> 
https://wiki.onap.org/display/DW/ONAP+on+Kubernetes+on+Rancher

I am unable to run the following commands, since the files are unavailable and 
it gives a 404 error for the same:

wget https://jira.onap.org/secure/attachment/ID/aaiapisimpledemoopenecomporg.cer
wget https://jira.onap.org/secure/attachment/1ID/onap-parameters.yaml
wget https://jira.onap.org/secure/attachment/ID/aai-cloud-region-put.json

It will be helpful for me if anyone could send me the active links for the 
following files.

Regards,
Pulkit
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

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

[onap-discuss] FW: ACUMOS ELK logging strategy

[DEY, SPONDON]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="DEY, SPONDON";SENT-BY="MAILTO:frank.obr...@amdocs.com":MAILTO:sd4
 3...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
DESCRIPTION;LANGUAGE=en-US:ONAP team\, you are welcome to the 2nd part of t
 his meeting where we will be focusing on logging/ELK spec/security sync po
 ints between the two open source projects.\n/michael\n\n-Original Appo
 intment-\nFrom: DEY\, SPONDON [mailto:sd4...@att.com]\nSent: Thursday\
 , May 31\, 2018 3:16 PM\nTo: DEY\, SPONDON\; Prudence Au\; Trevor Plestid\
 ; Michael O'Brien\; FERRO\, BOB\; KUNDURU\, RAMAKRISHNA\; CEFALU\, FARHEEN
 \; Amit Mishra3\; THAKORE\, SHISHIR B\; GUPTA\, PARICHAY\; LOTT\, CHRISTOP
 HER\; KRISTIANSEN JR.\, KENNETH G\; AGRAHARAM\, SANJAY\; CHEN\, CHUXIN\; A
 NAPAN-LAVALLE\, HECTOR A\; TALASILA\, MANOOP\; WELCH\, LORRAINE A\; TATTAV
 ARADA\, SUNDER\; MIR\, FARHAN\nCc: SHANOSKY\, CHRIS\nSubject: FW: ACUMOS E
 LK logging strategy\nWhen: Occurs every Thursday effective 4/12/2018 from 
 11:00 AM to 12:00 PM (UTC-05:00) Eastern Time (US & Canada).\nWhere: https
 ://connect7.uc.att.com/attinc3/meet/?ExEventID=86948116\n\n\nThe marker an
 d final log spec conversation will start at 11:30 AM EST\n\n-Original 
 Appointment-\nFrom: DEY\, SPONDON\nSent: Friday\, March 30\, 2018 10:2
 0 AM\nTo: DEY\, SPONDON\; KUNDURU\, RAMAKRISHNA\; CEFALU\, FARHEEN\; Amit 
 Mishra3\; THAKORE\, SHISHIR B\; GUPTA\, PARICHAY\; LOTT\, CHRISTOPHER\; KR
 ISTIANSEN JR.\, KENNETH G\; AGRAHARAM\, SANJAY\; CHEN\, CHUXIN\; ANAPAN-LA
 VALLE\, HECTOR A\; TALASILA\, MANOOP\; WELCH\, LORRAINE A\; TATTAVARADA\, 
 SUNDER\; MIR\, FARHAN\nCc: SHANOSKY\, CHRIS\; PLESTID\, TREVOR\nSubject: A
 CUMOS ELK logging strategy\nWhen: Occurs every Thursday effective 4/12/201
 8 from 11:00 AM to 12:00 PM (UTC-05:00) Eastern Time (US & Canada).\nWhere
 : https://connect7.uc.att.com/attinc3/meet/?ExEventID=86948116\n\n\nHi Tea
 m\,\n\nI am setting up this meeting to discuss and provide alignment and s
 trategic direction for the ACUMOS effort but focused around ELK.  I will s
 end out an Agenda prior to this meeting soon.\n\nHere is the att connect i
 nfo:\n\nYou are invited to attend an AT Connect iMeeting .\n\n\n\nTo con
 nect your COMPUTER to the Web conference:\n\n=
 =\n\nClick here: https://connect7.uc.att.com/attinc3/m
 eet/?ExEventID=86948116\n\n\n\n\n\nTo prepare in advance for the conferenc
 e (for all devices): https://connect7.uc.att.com/attinc3/Prepare/.\n\nTo v
 iew supported Operating Systems and devices: http://www.corp.att.com/attco
 nnectsupport/supporteddevices\n\n\n\n\n\nFor dialing-in only:\n\n-
 --\n\n1.Dial one of the numbers listed below\n\n2. When prompt
 ed\, enter the meeting access code: 6948116#\n\n  * Caller-Paid number
 : 312-777-1449\n\n  * Toll-Free Number (in USA): 888-331-6293.\n\n
   * Blackberry (Caller-Paid): 3127771449x6948116#\n\n  * iPhone / Andr
 oid (Caller-Paid): 3127771449\,\,6948116#\n\n  * Windows Phone (Caller
 -Paid): tel:3127771449\,\,6948116#\,\n\n  * A number in your country o
 r in a country close to you (may be toll free): https://www.teleconference
 .att.com/servlet/glbAccess?process=1=8883316293=69
 48116\n\n\n\n\n\nIf you are an AT Employee with a COU iPhone\, please go
 to  http://newcou.edc.cingular.net/_groups/COU/index.cfm?module=appStore
 tep=3=1=160=appStore to download the software from t
 he COU Appstore\n\n\n\nPowered by AT Connect.\n\n\n\n\n
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=TH;WKST=MO
SUMMARY;LANGUAGE=en-US:FW: ACUMOS ELK logging strategy 
DTSTART;TZID=Eastern Standard Time:20180412T11
DTEND;TZID=Eastern Standard Time:20180412T12
UID:CB744A97-64E2-4128-858E-A687E698F571
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180529T174810Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:22
LOCATION;LANGUAGE=en-US:https://connect7.uc.att.com/attinc3/meet/?ExEventID
 =86948116
X-MICROSOFT-CDO-APPT-SEQUENCE:22
X-MICROSOFT-CDO-OWNERAPPTID:2116284482
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:TRUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
BEGIN:VEVENT
SUMMARY:ACUMOS ELK logging strategy 
DTSTART;TZID=Eastern Standard Time:20180531T11
DTEND;TZID=Eastern Standard Time:20180531T12
UID:CB744A97-64E2-4128-858E-A687E698F571

[onap-discuss] Updated invitation: Papyrus Training Session (updated) @ Wed Jun 13, 2018 6am - 8am (PDT) (onap-discuss@lists.onap.org)

[kpaul]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20180613T13Z
DTEND:20180613T15Z
DTSTAMP:20180606T151610Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:50pg9d75m70t6bj96jcijms...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=jessie.jew...@oamtechnologies.com;X-NUM-GUESTS=0:mailto:jessie.jewi
 t...@oamtechnologies.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=onap-discuss@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@list
 s.onap.org
CREATED:20180605T201336Z
DESCRIPTION:Join from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/
 987452560https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fj%2F
 8672717796\;sa=D\;ust=1528730076362000\;usg=AFQjCNFa0jzOF1xcUWW
 8xvpsU0P4b0XHrA" target="_blank">\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nPlease do not edit t
 his section of the description.\n\nView your event at https://www.google.co
 m/calendar/event?action=VIEW=NTBwZzlkNzVtNzB0NmJqOTZqY2lqbXM2c2ggb25hcC
 1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0
 cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tY2Q5NzEzZDBjYWZ
 lMWE3Njk2MTFkODdlNzVmYmU3Mzc4ZWQ1NWY3Ng=America%2FLos_Angeles=en=
 0.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~::~:~::-
LAST-MODIFIED:20180606T151609Z
LOCATION:https://zoom.us/j/987452560
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:Papyrus Training Session (updated)
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Install ONAP Beijing Release

[Borislav Glozman]

Looks like something happened to helm repo and it is not running on your host.
Please run ‘nohup helm serve &’ and retry.

Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726
[amdocs-a]
Amdocs a Platinum member of 
ONAP

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Soumyarup Paul
Sent: Wednesday, June 6, 2018 1:47 PM
To: 'onap-discuss@lists.onap.org' 
Cc: Syed Atif Husain ; Gopal Sabhadiya 

Subject: [onap-discuss] Install ONAP Beijing Release

Hi All,

I am facing a few issues while installing the Beijing release.

1.   In the cd.sh script, should I uncomment this move file code
 if [ "$BRANCH" == "master" ]; then

echo "moving values.yaml to oom/kubernetes/"

 #sudo cp values.yaml oom/kubernetes/onap



If so, what is the encryption method used for password which I would 
need to provide here –

openStackEncryptedPasswordHere: "c124921a3a0efbe579782cde8227681e"



2.   If I try to install using the default values then I get the following 
error –

List of ONAP Modules - look for terminating pods

NAMESPACE NAME   READY STATUS
RESTARTS   AGE   IP  NODE

kube-system   heapster-76b8cd7b5-dl28v   1/1   Running   0  
7d10.42.34.140
blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net

kube-system   kube-dns-5d7b4487c9-6d6m2  3/3   Running   0  
7d10.42.207.251   
blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net

kube-system   kubernetes-dashboard-f9577fffd-k5snh   1/1   Running   0  
7d10.42.149.137   
blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net

kube-system   monitoring-grafana-997796fcf-qdps2 1/1   Running   0  
7d10.42.132.98
blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net

kube-system   monitoring-influxdb-56fdcd96b-xctvq1/1   Running   0  
7d10.42.208.55
blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net

kube-system   tiller-deploy-54bcc55dd5-scrbq 1/1   Running   0  
7d10.42.61.176
blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net

 deleting /dockerdata-nfs

chmod: cannot access '/dockerdata-nfs/onap': No such file or directory

chmod: cannot access '/dockerdata-nfs/dev': No such file or directory

pull new oom

Cloning into 'oom'...

remote: Total 16470 (delta 0), reused 16470 (delta 0)

Receiving objects: 100% (16470/16470), 24.04 MiB | 14.89 MiB/s, done.

Resolving deltas: 100% (8252/8252), done.

Checking connectivity... done.

moving values.yaml to oom/kubernetes/

start onap pods



[common]

make[1]: Entering directory '/root/oom/kubernetes'

make[2]: Entering directory '/root/oom/kubernetes/common'



[common]

make[3]: Entering directory '/root/oom/kubernetes/common'

==> Linting common

[INFO] Chart.yaml: icon is recommended



1 chart(s) linted, no failures

Successfully packaged chart and saved it to: 
/root/oom/kubernetes/dist/packages/common-2.0.0.tgz

make[3]: Leaving directory '/root/oom/kubernetes/common'



[mariadb-galera]

make[3]: Entering directory '/root/oom/kubernetes/common'

Hang tight while we grab the latest from your chart repositories...

...Unable to get an update from the "local" chart repository 
(http://127.0.0.1:8879/charts):

Get http://127.0.0.1:8879/charts/index.yaml: dial tcp 127.0.0.1:8879: 
getsockopt: connection refused

...Successfully got an update from the "stable" chart repository

Update Complete. ⎈Happy Helming!⎈

Saving 1 charts

Deleting outdated charts

==> Linting mariadb-galera

[INFO] Chart.yaml: icon is recommended



1 chart(s) linted, no failures

Successfully packaged chart and saved it to: 
/root/oom/kubernetes/dist/packages/mariadb-galera-2.0.0.tgz

make[3]: Leaving directory '/root/oom/kubernetes/common'



[mongo]

make[3]: Entering directory '/root/oom/kubernetes/common'

Hang tight while we grab the latest from your chart repositories...

...Unable to get an update from the "local" chart repository 
(http://127.0.0.1:8879/charts):

Get http://127.0.0.1:8879/charts/index.yaml: dial tcp 127.0.0.1:8879: 
getsockopt: connection refused

...Successfully got an update from the "stable" chart repository

Update Complete. ⎈Happy Helming!⎈

Saving 1 charts

Downloading common from repo http://127.0.0.1:8879/charts

Save error occurred:  could not download 
http://127.0.0.1:8879/charts/common-2.0.0.tgz: Get 
http://127.0.0.1:8879/charts/common-2.0.0.tgz: dial tcp 127.0.0.1:8879: 
getsockopt: connection refused

Deleting newly downloaded charts, restoring pre-update state

Error: could not download http://127.0.0.1:8879/charts/common-2.0.0.tgz: Get 
http://127.0.0.1:8879/charts/common-2.0.0.tgz: dial tcp 127.0.0.1:8879: 
getsockopt: 

Re: [onap-discuss] [modeling] Papyrus Training Session

[jessie jewitt]

A meeting announcement was sent out that this meeting was today. It is NEXT
Wednesday June 13th at 6AM.
Sorry for the inconvenience.
-Jessie

On Wed, Jun 6, 2018 at 4:52 AM, SCAGGS, KEVIN  wrote:

> All,
>
>
>
> We will use the following zoom meeting instead.
>
>
>
> https://zoom.us/j/987452560
>
>
>
> Regards,
>
> Kevin
>
>
>
>
>
> *From:* jessie jewitt 
> *Sent:* Monday, June 04, 2018 8:14 PM
> *To:* onap-discuss 
> *Cc:* MAYER, ANDREW J ; SCAGGS, KEVIN ;
> Brian Hedstrom 
> *Subject:* [modeling] Papyrus Training Session
>
>
>
> The VNFSDK Modeling team is hosting a Papyrus training session on
> Wednesday, June 13th at 6am Pacific / 9am Eastern / 9pm China time
>
> This session will cover:
>
>
>
> 1. How to install Papyrus
>
> 2. The value of using a modeling tool such as Papyrus within ONAP
>
> 3. How to use Papyrus alongside the wiki.
>
>
>
>
>
> We will be using Kevin's bridge:
>
> https://co
> 
> nnect2.uc.att.com/attinc/meet/?ExEventID=81618271=M
>
>
>
> Please plan on attending.
>
> -Jessie
>
>
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Invitation: [aai] Historical Data Tracking @ Weekly from 7am to 8am on Wednesday from Wed Mar 28 to Wed Mar 6, 2019 (PDT) (onap-discuss@lists.onap.org)

[REEHIL, WILLIAM E]

Hey folks,

In case your calendar invite didn't reflect the update, this Historical Data 
Tracking meeting has been canceled.

Thanks,

William Reehil
Active and Available Inventory
D2 PLATFORM & SYSTEMS DEVELOPMENT - Principal Member of Technical Staff
AT Services Middletown, NJ
O: (732) 420-7806 | C: (732) 865-5333



-Original Appointment-
From: AGGARWAL, MANISHA On Behalf Of ONAP Meetings and Events
Sent: Wednesday, March 28, 2018 9:25 AM
To: ONAP Meetings and Events; MULLER, ANDREW; NAIK, SOUMYA; FORSYTH, JAMES; 
MAHARAJH, ROBBY; onap-discuss@lists.onap.org; REEHIL, WILLIAM E
Subject: FW: [onap-discuss] Invitation: [aai] Historical Data Tracking @ Weekly 
from 7am to 8am on Wednesday from Wed Mar 28 to Wed Mar 6, 2019 (PDT) 
(onap-discuss@lists.onap.org)
When: Wednesday, June 06, 2018 10:00 AM-11:00 AM America/New_York.
Where: https://zoom.us/j/851671845


Just in case you are not subscribed to the onap-discuss calendar.

Manisha

-Original Appointment-
From: ONAP Meetings and Events 
[mailto:linuxfoundation.org_1rmtb5tpr3uc8f76fmflplo...@group.calendar.google.com]
Sent: Thursday, March 22, 2018 8:27 PM
To: ONAP Meetings and Events; FORSYTH, JAMES; 
onap-discuss@lists.onap.org
Subject: [onap-discuss] Invitation: [aai] Historical Data Tracking @ Weekly 
from 7am to 8am on Wednesday from Wed Mar 28 to Wed Mar 6, 2019 (PDT) 
(onap-discuss@lists.onap.org)
When: Occurs every Wednesday effective 3/28/2018 until 3/6/2019 from 10:00 AM 
to 11:00 AM America/New_York.
Where: https://zoom.us/j/851671845


more details 
>

[aai] Historical Data Tracking
When
Weekly from 7am to 8am on Wednesday from Wed Mar 28 to Wed Mar 6, 2019 
Pacific Time

Where

https://zoom.us/j/851671845
 
(map)

Calendar
onap-discuss@lists.onap.org

Who
*
kp...@linuxfoundation.org - creator

*
jf2...@att.com

*
onap-discuss@lists.onap.org



Hi there,

ONAP Meeting 10 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/851671845
Or iPhone one-tap :
US: +16699006833,,851671845# or +16465588656,,851671845#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855 
880 1246 (Toll Free)
Meeting ID: 851 671 845
International numbers available: 
https://zoom.us/zoomconference?m=6DMT8ODjPDZ_tABdAn2HCi0b1KnSta53




Going?   All events in this series:   

Re: [onap-discuss] Invitation: [multicloud] Weekly Meeting (Updated April 23, 2018) @ Weekly from 5pm to 6pm on Monday (PDT) (onap-discuss@lists.onap.org)

[GUPTA, ALOK]

Bin:

We need SDC ptl on instruction on how and where vnf or vnfc artifact is stored 
in asdc and how it can be retrieved. I know there are groups who are placing 
the yaml artifacts in SDCI think it is on the SDC GUI. I will poke around 
and see if I can find exact steps. For policy gui, I would reach out to Pam 
Dragosh policy ptl.


Regards,

Alok Gupta
732-420-7007
MT B2 3D30
ag1...@att.com

From: Yang, Bin 
Sent: Tuesday, June 5, 2018 8:33 PM
To: GUPTA, ALOK ; kp...@linuxfoundation.org; 
lxin...@vmware.com; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Invitation: [multicloud] Weekly Meeting (Updated 
April 23, 2018) @ Weekly from 5pm to 6pm on Monday (PDT) 
(onap-discuss@lists.onap.org)

Hi Alok,

   Great to know that, could you share the pointers to guide me how 
to onboard a VES yaml?  And hence how to fill Policy manually via its GUI? 
Thanks

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

From: GUPTA, ALOK [mailto:ag1...@att.com]
Sent: Tuesday, June 05, 2018 8:57 PM
To: Yang, Bin; kp...@linuxfoundation.org; 
lxin...@vmware.com; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Invitation: [multicloud] Weekly Meeting (Updated 
April 23, 2018) @ Weekly from 5pm to 6pm on Monday (PDT) 
(onap-discuss@lists.onap.org)

Bin:

Yes we can onboard VEs yaml files in the sdc. The automation wrt Policy picking 
up the VES yaml to auto populate GUI, I don't belive has been done. So one 
willhave to look at ymal manually and fill the Policy and/or configuration GUI.


Regards,

Alok Gupta
732-420-7007
MT B2 3D30
ag1...@att.com

From: Yang, Bin mailto:bin.y...@windriver.com>>
Sent: Monday, June 4, 2018 10:12 PM
To: GUPTA, ALOK mailto:ag1...@att.com>>; 
kp...@linuxfoundation.org; 
lxin...@vmware.com; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Invitation: [multicloud] Weekly Meeting (Updated 
April 23, 2018) @ Weekly from 5pm to 6pm on Monday (PDT) 
(onap-discuss@lists.onap.org)

Hi Alok,

   Appreciate your share the slides again.

   A general question follows: the slide "VES On-Boarding Artifact 
Use" mentioned that vendors/service providers could on-board these VES Artifact 
to SDC for Policy/Close Loop Creation/design, so is there any demo to showcase 
how to do that?

Thanks.

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

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of GUPTA, ALOK
Sent: Tuesday, June 05, 2018 8:49 AM
To: kp...@linuxfoundation.org; 
lxin...@vmware.com; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Invitation: [multicloud] Weekly Meeting (Updated 
April 23, 2018) @ Weekly from 5pm to 6pm on Monday (PDT) 
(onap-discuss@lists.onap.org)

Team:

Please find enclosed presentation used today. Also enclosed is VES summary and 
eventId use cases.

Please feel free to call me if you have questions.


Regards,

Alok Gupta
732-420-7007
MT B2 3D30
ag1...@att.com


-Original Appointment-
From: ONAP Meetings and Events 
mailto:linuxfoundation.org_1rmtb5tpr3uc8f76fmflplo...@group.calendar.google.com>>
Sent: Monday, April 23, 2018 8:55 AM
To: ONAP Meetings and Events; lxin...@vmware.com; 
onap-discuss@lists.onap.org
Subject: [onap-discuss] Invitation: [multicloud] Weekly Meeting (Updated April 
23, 2018) @ Weekly from 5pm to 6pm on Monday (PDT) 
(onap-discuss@lists.onap.org)
When: Monday, June 4, 2018 5:00 PM-6:00 PM America/Los_Angeles.
Where: 
https://zoom.us/j/9057041886


more details 

[onap-discuss] SSDC Distribution in Amsterdam

[FREEMAN, BRIAN D]

Libby,

DMAAP-157 is closed. We have run SDC model distribution in Amsterdam and 
Beijing thousands of times.

Your problem must be environment specific.


Do the following.


  1.  On the Message router VM - stop zookeeper, kafka and dmaap
  2.  Start zookeeper
  3.  Wait 30 seconds
  4.  Start kafka
  5.  Wait 30 seconds
  6.  Start dmaap


Use POSTMAN or Curl to do a GET against the topics in dmapp

http://{{mr}}:3904/topics/

you should see the list of topics

doe a HTTP GET agaisnt the SDC topic

http://{{mr}}:3904/events/SDC-DISTR-NOTIF-TOPIC-AUTO/group1/client1?timeout=5


do a HTTP POST against an unauthenticate test topic and confirm that you can do 
a GET against it


  1.  POST http://{{mr}}:3904 events/TESTTOPIC/
 *   Accept:application/json
 *   Content-Type:application/json
 *   { "test"}
  2.  GET http://{{mr}}:3904 events/TESTTOPIC/
  3.  You may need to do the POST/GET twice due to the way initial sessions are 
created

This would confirm that DMaaP is working

I would then restart the SDC-BE process and you should see SDC on the DMaaP 
writer list


http://{{mr}}:3904/topics/SDC-DISTR-STATUS-TOPIC-AUTO

Should list out a structure with all the clients subscribing to the topic.


Brian

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

[onap-discuss] [vvp] VVP committer actions

[WRIGHT, STEVEN A]

The following committers have been removed as active committers on the vnfrqts 
project:

  *   Eric Sundelof
  *   Lingli Deng
  *   Edan Binshtok

I would like to thank them for their service to the ONAP/VNFRQTS community and 
wish them well in their future endeavours.

A committer nomination request for Steven Stark is posted 
here.


best regards
Steven Wright, MBA, PhD, JD.
[Tech Integration]
AT Services Inc.
1057 Lenox Park Blvd NE, STE 4D28
Atlanta, GA 30319

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

Re: [onap-discuss] [modeling] Papyrus Training Session

[SCAGGS, KEVIN]

All,

We will use the following zoom meeting instead.

https://zoom.us/j/987452560

Regards,
Kevin


From: jessie jewitt 
Sent: Monday, June 04, 2018 8:14 PM
To: onap-discuss 
Cc: MAYER, ANDREW J ; SCAGGS, KEVIN ; Brian 
Hedstrom 
Subject: [modeling] Papyrus Training Session

The VNFSDK Modeling team is hosting a Papyrus training session on Wednesday, 
June 13th at 6am Pacific / 9am Eastern / 9pm China time
This session will cover:

1. How to install Papyrus
2. The value of using a modeling tool such as Papyrus within ONAP
3. How to use Papyrus alongside the wiki.


We will be using Kevin's bridge:
https://connect2.uc.att.com/attinc/meet/?ExEventID=81618271=M

Please plan on attending.
-Jessie

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

[onap-discuss] Rancher Based Deployment - 404 Error

[Pulkit Walia]

Hi All,

I am trying to deploy ONAP on Kubernetes using Rancher.
In the following link --> 
https://wiki.onap.org/display/DW/ONAP+on+Kubernetes+on+Rancher

I am unable to run the following commands, since the files are unavailable and 
it gives a 404 error for the same:

wget https://jira.onap.org/secure/attachment/ID/aaiapisimpledemoopenecomporg.cer
wget https://jira.onap.org/secure/attachment/1ID/onap-parameters.yaml
wget https://jira.onap.org/secure/attachment/ID/aai-cloud-region-put.json

It will be helpful for me if anyone could send me the active links for the 
following files.

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

[onap-discuss] Install ONAP Beijing Release

[Soumyarup Paul]

Hi All,

I am facing a few issues while installing the Beijing release.

1.   In the cd.sh script, should I uncomment this move file code
 if [ "$BRANCH" == "master" ]; then

echo "moving values.yaml to oom/kubernetes/"

 #sudo cp values.yaml oom/kubernetes/onap



If so, what is the encryption method used for password which I would 
need to provide here –

openStackEncryptedPasswordHere: "c124921a3a0efbe579782cde8227681e"



2.   If I try to install using the default values then I get the following 
error –

List of ONAP Modules - look for terminating pods

NAMESPACE NAME   READY STATUS
RESTARTS   AGE   IP  NODE

kube-system   heapster-76b8cd7b5-dl28v   1/1   Running   0  
7d10.42.34.140
blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net

kube-system   kube-dns-5d7b4487c9-6d6m2  3/3   Running   0  
7d10.42.207.251   
blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net

kube-system   kubernetes-dashboard-f9577fffd-k5snh   1/1   Running   0  
7d10.42.149.137   
blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net

kube-system   monitoring-grafana-997796fcf-qdps2 1/1   Running   0  
7d10.42.132.98
blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net

kube-system   monitoring-influxdb-56fdcd96b-xctvq1/1   Running   0  
7d10.42.208.55
blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net

kube-system   tiller-deploy-54bcc55dd5-scrbq 1/1   Running   0  
7d10.42.61.176
blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net

 deleting /dockerdata-nfs

chmod: cannot access '/dockerdata-nfs/onap': No such file or directory

chmod: cannot access '/dockerdata-nfs/dev': No such file or directory

pull new oom

Cloning into 'oom'...

remote: Total 16470 (delta 0), reused 16470 (delta 0)

Receiving objects: 100% (16470/16470), 24.04 MiB | 14.89 MiB/s, done.

Resolving deltas: 100% (8252/8252), done.

Checking connectivity... done.

moving values.yaml to oom/kubernetes/

start onap pods



[common]

make[1]: Entering directory '/root/oom/kubernetes'

make[2]: Entering directory '/root/oom/kubernetes/common'



[common]

make[3]: Entering directory '/root/oom/kubernetes/common'

==> Linting common

[INFO] Chart.yaml: icon is recommended



1 chart(s) linted, no failures

Successfully packaged chart and saved it to: 
/root/oom/kubernetes/dist/packages/common-2.0.0.tgz

make[3]: Leaving directory '/root/oom/kubernetes/common'



[mariadb-galera]

make[3]: Entering directory '/root/oom/kubernetes/common'

Hang tight while we grab the latest from your chart repositories...

...Unable to get an update from the "local" chart repository 
(http://127.0.0.1:8879/charts):

Get http://127.0.0.1:8879/charts/index.yaml: dial tcp 127.0.0.1:8879: 
getsockopt: connection refused

...Successfully got an update from the "stable" chart repository

Update Complete. ⎈Happy Helming!⎈

Saving 1 charts

Deleting outdated charts

==> Linting mariadb-galera

[INFO] Chart.yaml: icon is recommended



1 chart(s) linted, no failures

Successfully packaged chart and saved it to: 
/root/oom/kubernetes/dist/packages/mariadb-galera-2.0.0.tgz

make[3]: Leaving directory '/root/oom/kubernetes/common'



[mongo]

make[3]: Entering directory '/root/oom/kubernetes/common'

Hang tight while we grab the latest from your chart repositories...

...Unable to get an update from the "local" chart repository 
(http://127.0.0.1:8879/charts):

Get http://127.0.0.1:8879/charts/index.yaml: dial tcp 127.0.0.1:8879: 
getsockopt: connection refused

...Successfully got an update from the "stable" chart repository

Update Complete. ⎈Happy Helming!⎈

Saving 1 charts

Downloading common from repo http://127.0.0.1:8879/charts

Save error occurred:  could not download 
http://127.0.0.1:8879/charts/common-2.0.0.tgz: Get 
http://127.0.0.1:8879/charts/common-2.0.0.tgz: dial tcp 127.0.0.1:8879: 
getsockopt: connection refused

Deleting newly downloaded charts, restoring pre-update state

Error: could not download http://127.0.0.1:8879/charts/common-2.0.0.tgz: Get 
http://127.0.0.1:8879/charts/common-2.0.0.tgz: dial tcp 127.0.0.1:8879: 
getsockopt: connection refused

Makefile:37: recipe for target 'dep-mongo' failed

make[3]: *** [dep-mongo] Error 1

make[3]: Leaving directory '/root/oom/kubernetes/common'

Makefile:30: recipe for target 'mongo' failed

make[2]: *** [mongo] Error 2

make[2]: Leaving directory '/root/oom/kubernetes/common'

Makefile:39: recipe for target 'make-common' failed

make[1]: *** [make-common] Error 2

make[1]: Leaving directory '/root/oom/kubernetes'

Makefile:35: recipe for target 'common' failed

make: *** [common] Error 2



[onap]

make[1]: Entering directory '/root/oom/kubernetes'

[onap-discuss] Can not import VSP

[Huang, Haibin]

Hi Michel,

We have write CPE accord to R2 DM, please see attachment vgw.csar.
We execute following steps:

1. We create VF and import vgw.csar.

2. We import VSP which we just create, but we encounter below error. Can 
you help me to see where  the csar file is wrong?



[cid:image001.jpg@01D3FDAC.C81814E0]

Thank you very much!
---
Huang.haibin
11628530
86+18106533356



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

Re: [onap-discuss] [ONAP Helpdesk #56955] RE: Beijing Release: Last Mile

[denghu...@huawei.com via RT]

Dear Jessica,

Sorry for late,

https://jenkins.onap.org/view/modeling/job/modeling-toscaparsers-javatoscachecker-master-javatoscachecker-release-version-java-daily/209/
https://jenkins.onap.org/view/modeling/job/modeling-toscaparsers-nfvparser-master-nfvparser-release-version-java-daily/127/

thanks

DENG Hui


-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Wednesday, June 6, 2018 1:00 PM
To: denghui (L) 
Cc: Gildas Lanilis ; j...@research.att.com; 
onap-discuss@lists.onap.org; onap-rele...@lists.onap.org; 
rittwik.j...@gmail.com; shang.xiaod...@zte.com.cn; yangya...@chinamobile.com
Subject: [ONAP Helpdesk #56955] RE: [onap-discuss] Beijing Release: Last Mile

Dear Deng, 

Thanks, but I need you to give me the links to the Jenkins jobs that generated 
these please. 

I cannot perform a release without them.

Thanks!
Jess
 
On Tue Jun 05 22:48:45 2018, denghu...@huawei.com wrote:
> Hi Jess,
> 
> This is for modeling part, thanks a lot:
> 
> Javatoscachecker:  /org/onap/modeling/toscaparsers/Checker/1.2.0-
> SNAPSHOT/Checker-1.2.0-20180605.124309-
> 60.jar tent/org/onap/modeling/toscaparsers/Checker/1.2.0-
> SNAPSHOT/Checker-1.2.0-20180605.124309-60.jar>
> NFVParser:  /org/onap/modeling/toscaparsers/nfvparser/modeling-
> toscaparsers-nfvparser/1.1.0-SNAPSHOT/modeling-toscaparsers-nfvparser-
> 1.1.0-20180329.050338-
> 7.zip ent/org/onap/modeling/toscaparsers/nfvparser/modeling-
> toscaparsers-nfvparser/1.1.0-SNAPSHOT/modeling-toscaparsers-nfvparser-
> 1.1.0-20180329.050338-7.zip>
> 
> Deng Hui
> 
> From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss- 
> boun...@lists.onap.org] On Behalf Of Jessica Wagantall
> Sent: Wednesday, June 6, 2018 6:16 AM
> To: Gildas Lanilis 
> Cc: onap-rele...@lists.onap.org; onap-discuss@lists.onap.org
> Subject: Re: [onap-discuss] Beijing Release: Last Mile
> 
> No request received yet also from the modeling team.
> 
> Thanks!
> Jess
> 
> On Tue, Jun 5, 2018 at 3:14 PM, Jessica Wagantall 
> mailto:jwagant...@linuxfoundation.org>
> >
> wrote:
> Dear Gildas,
> 
> Here is an update on the pending items:
> 
> *** MUSIC *** New release version 2.5.5 needed ***
> 
> - Working with Tom on this now. We should be releasing soon.
> Reference: #56927: Music Jar Release 2.5.5
> 
> *** VID *** New clarification from the team ***
> 
> - The request was placed to make a docker release but I noticed
>   their maven artifacts haven't been released for the specific version 
> used
>   to build their docker images. Do we approve a release of those too?
> Reference: #56922: VID docker release
> 
> *** AAF *** Pending Ram's Approval ***
> 
> - Docker release for  onap/aaf/sms and onap/aaf/smsquorumclient 2.0.0
> - Java artifacts 2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-
> 8.jar repositories;snapshots~browsestorage~/org/onap/aaf/sms/sms-
> client/2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-8.jar>
> Reference: #56662: Artifacts for Release
> 
> No release request yet from multicloud or usecase-ui teams!
> 
> Thanks!
> Jess
> 
> On Mon, Jun 4, 2018 at 12:27 PM, Jessica Wagantall 
> mailto:jwagant...@linuxfoundation.org>
> >
> wrote:
> Thanks a lot for this Gildas,
> 
> Due to the importance of these releases, I will help posting here the 
> blockers we encounter in the RT tickets.
> 
> Here are some blockers:
> 
> *** AAF *** Pending Ram's Approval ***
> 
> - Docker release for  onap/aaf/sms and onap/aaf/smsquorumclient 2.0.0
> - Java artifacts 2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-
> 8.jar repositories;snapshots~browsestorage~/org/onap/aaf/sms/sms-
> client/2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-8.jar>
> Reference: #56662: Artifacts for Release
> 
> *** DMAAP *** Pending Ram's Approval ***
> 
> - Docker release for onap/dmaap/dmaap-mr:1.1.4
> Reference: #56857: Move docker image to release repository
> 
> *** VFC *** Yan to clarify ***
> 
> - Email sent for 8 maven artifacts to be released, but email mentions 
> also docker images needed and no link to docker images jobs
> - Do we just need to release the maven artifacts? if docker images 
> need release, please update request with corresponding docker links 
> from Jenkins
> Reference: #56821: Please help to release VF-C R2 artifacts to 
> releases repo
> 
> 
> Thanks!
> Jess
> 
> On Mon, Jun 4, 2018 at 7:33 AM, Gildas Lanilis 
> mailto:gildas.lani...@huawei.com>> wrote:
> Hi PTLs,
> 
> This email is to summarize on the latest activities to reach Beijing 
> Release Sign-Off this Thursday, June 7, 2018.
> 
> 1.   Docker image: All projects that need to Release a new Docker
> Image (and thus update accordingly the Docker manifest file) must 
> email LF Helpdesk by 2 pm PDT on Tuesday, June 5 including a link to 
> the proper 

Re: [onap-discuss] [ONAP Helpdesk #56955] RE: Beijing Release: Last Mile

[denghui (L)]

Dear Jessica,

Sorry for late,

https://jenkins.onap.org/view/modeling/job/modeling-toscaparsers-javatoscachecker-master-javatoscachecker-release-version-java-daily/209/
https://jenkins.onap.org/view/modeling/job/modeling-toscaparsers-nfvparser-master-nfvparser-release-version-java-daily/127/

thanks

DENG Hui


-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Wednesday, June 6, 2018 1:00 PM
To: denghui (L) 
Cc: Gildas Lanilis ; j...@research.att.com; 
onap-discuss@lists.onap.org; onap-rele...@lists.onap.org; 
rittwik.j...@gmail.com; shang.xiaod...@zte.com.cn; yangya...@chinamobile.com
Subject: [ONAP Helpdesk #56955] RE: [onap-discuss] Beijing Release: Last Mile

Dear Deng, 

Thanks, but I need you to give me the links to the Jenkins jobs that generated 
these please. 

I cannot perform a release without them.

Thanks!
Jess
 
On Tue Jun 05 22:48:45 2018, denghu...@huawei.com wrote:
> Hi Jess,
> 
> This is for modeling part, thanks a lot:
> 
> Javatoscachecker:  /org/onap/modeling/toscaparsers/Checker/1.2.0-
> SNAPSHOT/Checker-1.2.0-20180605.124309-
> 60.jar tent/org/onap/modeling/toscaparsers/Checker/1.2.0-
> SNAPSHOT/Checker-1.2.0-20180605.124309-60.jar>
> NFVParser:  /org/onap/modeling/toscaparsers/nfvparser/modeling-
> toscaparsers-nfvparser/1.1.0-SNAPSHOT/modeling-toscaparsers-nfvparser-
> 1.1.0-20180329.050338-
> 7.zip ent/org/onap/modeling/toscaparsers/nfvparser/modeling-
> toscaparsers-nfvparser/1.1.0-SNAPSHOT/modeling-toscaparsers-nfvparser-
> 1.1.0-20180329.050338-7.zip>
> 
> Deng Hui
> 
> From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss- 
> boun...@lists.onap.org] On Behalf Of Jessica Wagantall
> Sent: Wednesday, June 6, 2018 6:16 AM
> To: Gildas Lanilis 
> Cc: onap-rele...@lists.onap.org; onap-discuss@lists.onap.org
> Subject: Re: [onap-discuss] Beijing Release: Last Mile
> 
> No request received yet also from the modeling team.
> 
> Thanks!
> Jess
> 
> On Tue, Jun 5, 2018 at 3:14 PM, Jessica Wagantall 
> mailto:jwagant...@linuxfoundation.org>
> >
> wrote:
> Dear Gildas,
> 
> Here is an update on the pending items:
> 
> *** MUSIC *** New release version 2.5.5 needed ***
> 
> - Working with Tom on this now. We should be releasing soon.
> Reference: #56927: Music Jar Release 2.5.5
> 
> *** VID *** New clarification from the team ***
> 
> - The request was placed to make a docker release but I noticed
>   their maven artifacts haven't been released for the specific version 
> used
>   to build their docker images. Do we approve a release of those too?
> Reference: #56922: VID docker release
> 
> *** AAF *** Pending Ram's Approval ***
> 
> - Docker release for  onap/aaf/sms and onap/aaf/smsquorumclient 2.0.0
> - Java artifacts 2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-
> 8.jar repositories;snapshots~browsestorage~/org/onap/aaf/sms/sms-
> client/2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-8.jar>
> Reference: #56662: Artifacts for Release
> 
> No release request yet from multicloud or usecase-ui teams!
> 
> Thanks!
> Jess
> 
> On Mon, Jun 4, 2018 at 12:27 PM, Jessica Wagantall 
> mailto:jwagant...@linuxfoundation.org>
> >
> wrote:
> Thanks a lot for this Gildas,
> 
> Due to the importance of these releases, I will help posting here the 
> blockers we encounter in the RT tickets.
> 
> Here are some blockers:
> 
> *** AAF *** Pending Ram's Approval ***
> 
> - Docker release for  onap/aaf/sms and onap/aaf/smsquorumclient 2.0.0
> - Java artifacts 2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-
> 8.jar repositories;snapshots~browsestorage~/org/onap/aaf/sms/sms-
> client/2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-8.jar>
> Reference: #56662: Artifacts for Release
> 
> *** DMAAP *** Pending Ram's Approval ***
> 
> - Docker release for onap/dmaap/dmaap-mr:1.1.4
> Reference: #56857: Move docker image to release repository
> 
> *** VFC *** Yan to clarify ***
> 
> - Email sent for 8 maven artifacts to be released, but email mentions 
> also docker images needed and no link to docker images jobs
> - Do we just need to release the maven artifacts? if docker images 
> need release, please update request with corresponding docker links 
> from Jenkins
> Reference: #56821: Please help to release VF-C R2 artifacts to 
> releases repo
> 
> 
> Thanks!
> Jess
> 
> On Mon, Jun 4, 2018 at 7:33 AM, Gildas Lanilis 
> mailto:gildas.lani...@huawei.com>> wrote:
> Hi PTLs,
> 
> This email is to summarize on the latest activities to reach Beijing 
> Release Sign-Off this Thursday, June 7, 2018.
> 
> 1.   Docker image: All projects that need to Release a new Docker
> Image (and thus update accordingly the Docker manifest file) must 
> email LF Helpdesk by 2 pm PDT on Tuesday, June 5 including a link to 
> the proper