[onap-discuss] [ONAP Helpdesk #55152] [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April

[Jessica Wagantall via RT]

Dear Michael,

I wonder if this was a case of an old Snapshot that got removed by our
cleanup tasks. 
We have a daily task that cleans up any old Snapshots older than 16 days. 

This is the job that re-created this binary:
https://jenkins.onap.org/view/ccsdk/job/ccsdk-distribution-master-docker-java-daily/308/console

Do you think this was the case?

Thanks!
Jess

On Tue Apr 24 17:18:52 2018, frank.obr...@amdocs.com wrote:
> LF,
>   Just would like to understand what happened to this image that broke
> SDNC and APPC for a couple days
> 
> https://jira.onap.org/browse/SDNC-285
> https://jira.onap.org/browse/APPC-856
> 
> From the logs it looks like the SNAPSHOT image was returned 4 days ago
> - before the 20th of April the dockers failed to pull.
> https://nexus3.onap.org/#browse/browse:docker.snapshot:v2%2Fonap%2Fccsdk-
> dgbuilder-image%2Fmanifests%2F0.2.1-SNAPSHOT
> 
> Blob created
> 
> Fri Apr 20 2018 09:11:26 GMT-0400 (Eastern Daylight Time)
> 
> Blob updated
> 
> Tue Apr 24 2018 09:27:11 GMT-0400 (Eastern Daylight Time)
> 
> 
> When these images disappear for a while - the pods fail to come up.
> 
> 
> 
> Thank you
> /michael
> 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] Jenkins is down... investigating

[Jessica Wagantall]

Looks like we are back on track now... checking those clamp jobs too omg :(

On Tue, Apr 24, 2018 at 4:53 PM, Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> https://status.linuxfoundation.org/incidents/y03hqvtkystb
>
> for more info..
>
> On Tue, Apr 24, 2018 at 4:46 PM, Jessica Wagantall <
> jwagant...@linuxfoundation.org> wrote:
>
>> Dear team,
>>
>> Looks like Jenkins is down for the moment.
>>
>> I am not investigating the issue,
>>
>> thanks!
>> Jess
>>
>
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Jenkins is down... investigating

[Jessica Wagantall]

https://status.linuxfoundation.org/incidents/y03hqvtkystb

for more info..

On Tue, Apr 24, 2018 at 4:46 PM, Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Dear team,
>
> Looks like Jenkins is down for the moment.
>
> I am not investigating the issue,
>
> thanks!
> Jess
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] ONAP on Kubernetes

[ANAPAN-LAVALLE, HECTOR A]

Hi All,



I have also been testing the stability of ONAP in K8S/OOM/Rancher approach in 
TLAB, and have been seeing the same problems as described below when running a 
complete ONAP instance for more than 1 day. We have been mainly using the 
Portal application (going into the VNC console, then into the Portal GUI).



Some observations made from the testing so far:



- After running SAR Linux stats for some days on a complete ONAP instance 
(Amsterdam), It seems like a full ONAP instance in a single VM should have at 
least 120-180 GB of RAM along with some swap memory allocate in order for the 
cluster to not fail.



- Scaling up the Rancher's K8S Environment's services to more than 1 container 
which is the default (esp. the rancher-ingress-controller) is important since 
this service receives all API/curl requests exposed from K8S cluster.



I have also seen a more reliable ONAP instance when K8S is deployed in a 
multi-node/HA environment in a deployment of 1 Rancher VM, 1 MySQL VM as its 
external DB, and 7 K8S VMs (3 data plane nodes, 2 orch nodes, and 2 compute 
nodes - all can serve as compute nodes though)







I wanted to confirm that it does seem like the heap size ends up being the most 
important one to troubleshoot and it appears (from the JIRA issues below) that 
this needs to be fixed at the application level along with the limiting 
resources (or just stop trying to spawn up k8s deployments failing because of 
resource shortage)?



Thanks,

Hector







Hi A. Seaudi,



I'm really only speculating here but if there was a resource leak (memory or 
storage) that consumes everything on a node (physical machine or VM) the 
containers on that node will fail and Kubernetes will try to restart them. If 
there are insufficient resources the pod(s) will remain in "init" status until 
there are sufficient resources (say by adding a new node to the Kubernetes 
cluster).



The Beijing release is in the integration phase now and one of the major goals 
of the release was to achieve stability.  It would be great if you were willing 
to switch your testing to Beijing so we can identify problems like resource 
leaks quickly.  We want Beijing to be production ready so the more hardening we 
do the better.



Cheers,

Roger





From: "abdelmuhaimen.seaudi at 
orange.com" 
https://lists.onap.org/mailman/listinfo/onap-discuss>>

Date: Saturday, April 14, 2018 at 1:00 PM

To: Michael O'Brien https://lists.onap.org/mailman/listinfo/onap-discuss>>, Roger 
Maitland https://lists.onap.org/mailman/listinfo/onap-discuss>>, 
"onap-discuss at 
lists.onap.org" 
https://lists.onap.org/mailman/listinfo/onap-discuss>>

Subject: RE: [onap-discuss] ONAP on Kubernetes



Hi, I started with another clean vm, and now OOM is running fine.



However, I am interested to know why many pods return to "init" status after 
one or two days running.



Thanks



A. Seaudi



From: SEAUDI Abdelmuhaimen OBS/CSO

Sent: Saturday, April 14, 2018 3:11 PM

To: Michael O'Brien; Roger Maitland; onap-discuss at 
lists.onap.org

Subject: RE: [onap-discuss] ONAP on Kubernetes

Hi,



I was able to clean my system and close down port 10250, and the cpu issue is 
now resolved.



However, after a day or 2 runnnig OOM, i find many of the pods are now in init 
status, and i need to "./deleteAll -n onap -a aai" for example, and 
"./createAll -n onap -a aai" again to resume the pods working.



I worked like that for a while, but now i am facing errors similar to below, 
and i cannot get the pods to run again.



onap-message-router   dmaap-3126594942-cfm9n 0/1   rpc 
error: code = 2 desc = failed to start container 
"74b8d5d04b693c432a4b21a03c272418451eccdc54305330d998bfee0d532a59

": Error response from daemon: {"message":"invalid header field value \"oci 
runtime error: container_linux.go:247: starting container process caused 
\\\"process_linux.go:359: container init

 caused \\\"rootfs_linux.go:53: mounting 
\\\"/dockerdata-nfs/onap/message-router/dmaap/cadi.properties\\\"
 to rootfs \\\"/var/lib/docker/aufs/mnt/737

6ab454562d2c60dccf7a0a24f3a14b7ee33461f50487b8da6e1b358f5511b\\\" 
at 
\\\"/var/lib/docker/aufs/mnt/7376ab454562d2c60dccf7a0a24f3a14b7ee33461f50487b8da6e1b358f5511b/ap

pl/dmaapMR1/etc/cadi.properties\\\" caused \\\"not a 
directory\\\"\\\"\\\"\\n\""}   3  1m



Any idea what this error means ?



I tried to use a clean vm and pulling 
https://jira.onap.org/secure/attachment/11421/oom_rancher_setup.sh and 
https://jira.onap.org/secure/attachment/11413/cd.sh but i get the same result.



Thanks



A. Seaudi



From: Michael O'Brien [Frank.Obrien at 

[onap-discuss] Jenkins is down... investigating

[Jessica Wagantall]

Dear team,

Looks like Jenkins is down for the moment.

I am not investigating the issue,

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

[onap-discuss] ONAP platform deployment no successful

[ANAPAN-LAVALLE, HECTOR A]

Hi Santi,



For the Amsterdam release:



-I have come across that same error when I deployed ONAP in a multi-node/vm 
HA Kubernetes version of Rancher 
(https://rancher.com/docs/rancher/v1.6/en/kubernetes/resiliency-planes/) but 
not when the K8S cluster is hosted on a single VM only, so wondering if you 
tried doing this. One thing to make sure is to try using the latest supported 
version of docker for rancher which is 17.03.x I believe 
(https://rancher.com/docs/rancher/v1.6/en/hosts/#supported-docker-versions).

-Also, I used the README.md when installing ONAP using the OOM Amsterdam 
release (running createConfig.sh -n onap to create the namespace first, then 
running createAll.sh -n onap to create the ONAP instance)





For the Beijing release:



-While the code is not stable enough yet, there was an issue with the 
docker image registry (nexus3.onap.org) for the past few weeks but my 
understanding is that it has been solved.

-Also, you may want to look into having a local docker proxy that pulls the 
images from the LF docker registry to pull the images faster and more 
consistently (https://docs.docker.com/registry/recipes/mirror/). Another option 
is to download your own local nexus3 OSS repo in its own instance, and use it 
as a docker registry to proxy the images from nexus3.onap.org.



=

=

=







Hi all,



I've been trying to deploy the ONAP entire platform in my local environment

following the official documentation without the desired results:



   - First, I tried the amsterdam release installation:

  - kubectl 1.7.7

  - rancher 1.6.10

  - helm 2.3.0

  - docker 1.12

  - onap deployment using oom:

 - install/deployment/cd.sh

 - oom/kubernetes/oneclick/createAll.sh



Some of the pods are returning errors like:



Error syncing pod

Back-off restarting failed container

(combined from similar events): Error: failed to start container

"filebeat-onap-aai-model-loader": Error response from daemon:

{"*message":"invalid

header field value* \"oci runtime error: container_linux.go:247: starting

container process caused \\\"process_linux.go:359: container init caused

\\\"rootfs_linux.go:53: mounting

\\\"/dockerdata-nfs/onap/log/filebeat/logback/filebeat.yml\\\"

to rootfs

\\\"/var/lib/docker/aufs/mnt/5c0516a9e0641c993fda14a5818d53b59ff4342da146d52a3b58aaf045ce6295\\\"

at

\\\"/var/lib/docker/aufs/mnt/5c0516a9e0641c993fda14a5818d53b59ff4342da146d52a3b58aaf045ce6295/usr/share/filebeat/filebeat.yml\\\"

caused \\\"not a directory\\\"\\\"\\\"\\n\""}





   - Then, I tried with beijing/master:

  - kubectl 1.8.6

  - rancher 1.6.14

  - helm 2.6.1

  - docker 17.03

  - onap deployment using helm install local/onap



Some of the pods are not starting because they cannot pull the image. It

seems that large images produces a timeout. I found something related with

increasing a kubelet config parameter, but the followed k8s installation

guide does not produce any kubelet installation.



It seems that the code is not stable enough, but i saw that many people are

working with the platform so is possible to deploy it.



How did you deploy the platform? Is there any hidden step that I'm missing?



Thanks,



BR, Santi

*Santiago Rodríguez García* | Senior Analyst

T/ + 34 986 410 091 (ext) 227

www.optaresolutions.com

[image: Optare Solutions] 

-- next part --

An HTML attachment was scrubbed...

URL: 


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

Re: [onap-discuss] ONAP using heat templates

[ANAPAN-LAVALLE, HECTOR A]

Pavithra,

Not sure if you fixed this problem already, but just a heads up that the 
nexus3.onap.org docker registry was downloading images very slowly or not at 
all, and that has been fixed by LF from what I know.

If your problem has been resolved, please let us know.

=
=

Couple of things:


1.   Those heat templates look like the pre-Amsterdam version of ONAP, you 
should probably move to R1 (Amsterdam) version:

https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=heat/ONAP;h=64815cec035a3e9819699309375991f519e9f23e;hb=refs/heads/amsterdam


2.   If you are required to go through a proxy server to reach the 
internet, then you will have to make updates to the template to define 
http_proxy and https_proxy environment variables




From: onap-discuss-bounces at lists.onap.org [mailto:onap-discuss-bounces at 
lists.onap.org] On Behalf Of FREEMAN, BRIAN D
Sent: Friday, April 06, 2018 8:50 AM
To: Pavithra R13 ; onap-discuss at lists.onap.org
Subject: Re: [onap-discuss] ONAP using heat templates

Do you VM's have access to the internet. Check the cloud-init logs and see if 
there were error messages trying to resolve nexus3.onap.org and the like.

Most likely the VM's are blank becuase the vm_install and vm_init scipts cant 
reach the internet (or at least that is the most likely scenario).

Make sure public dns is on your external network.

Brian


From: onap-discuss-bounces at lists.onap.org [mailto:onap-discuss-bounces at lists.onap.org] On Behalf Of 
Pavithra R13
Sent: Friday, April 06, 2018 3:37 AM
To: onap-discuss at lists.onap.org
Subject: [onap-discuss] ONAP using heat templates

Hi All
I am trying to install ONAP using heat templates on Openstack Pike. I 
downloaded the template and environment file from the link 
https://nexus.onap.org/content/sites/raw/org.openecomp.demo/heat/OpenECOMP/1.0.0
 . The stack is up and am able to access the VMs. But am not able to access the 
ONAP PORTAL. When I logged into the portal VM and ran "docker ps -a" I could 
see there is no docker installed. So I guess the installation might not have 
completed successfully and just empty VMs are created. Kindly let me know how 
to check the installation or let me know any other working heat templates.
Thanks & Regards,
Pavithra R



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 

-- next part --
An HTML attachment was scrubbed...
URL: 

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

[onap-discuss] [LOG] Logging specification review close off for (Cassablanca) - meet 4

[Michael O'Brien]

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=Michael O'Brien:MAILTO:frank.obr...@amdocs.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:Team\,\n  Meeting: my zoom: https://zoom.us/j/79
 39937123\n  Time 1130 EDT GMT-5 just after the TSC meet (no Integration te
 sting meet on thu)\n  SCOPE: you only need to come to discuss the MDC fiel
 ds in the logging specification if you would like.\n  Specifically the Mar
 kers and how we may consolidate 5+ log files into one using a combination 
 of the MDC’s and Markers to target specific logs\n\n\n   We will be havi
 ng a continuation of our review of the logging specification for Casablanc
 a – AT has been driving a lot of these discussions with us – which i
 s very good.\nWe finalized a major portion of the required fields and 
 will close off the spec on thu.\n\n   Scope is for logging committers and 
 contributors – anyone from other projects are welcome.\n   Specifically 
 we will be narrowing down the required MDC’s and targeting how to handle
  external BSS/clients tracking requestID/invocationID graphs\n\nSpec under
  review\nhttps://wiki.onap.org/pages/viewpage.action?pageId=28378955\nnote
 s\nhttps://wiki.onap.org/display/DW/LOG+Meeting+Minutes+2018-04-10\nhttps:
 //wiki.onap.org/display/DW/LOG+Meeting+Minutes+2018-04-17\nhttps://wiki.on
 ap.org/display/DW/LOG+Meeting+Minutes+2018-04-24\n\n\nthank you\n/michael\
 n\n
SUMMARY;LANGUAGE=en-US:[LOG] Logging specification review close off for (Ca
 ssablanca) - meet 4
DTSTART;TZID=Eastern Standard Time:20180426T113000
DTEND;TZID=Eastern Standard Time:20180426T123000
UID:04008200E00074C5B7101A82E008907A086BF3DBD301000
 0146262FB12C0CA4A9CE78C4B411C9DFA
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180424T214104Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:http://zoom.us/j/7939937123
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:548947938
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April

[Michael O'Brien]

LF,
  Just would like to understand what happened to this image that broke SDNC and 
APPC for a couple days

https://jira.onap.org/browse/SDNC-285
https://jira.onap.org/browse/APPC-856

  From the logs it looks like the SNAPSHOT image was returned 4 days ago - 
before the 20th of April the dockers failed to pull.
https://nexus3.onap.org/#browse/browse:docker.snapshot:v2%2Fonap%2Fccsdk-dgbuilder-image%2Fmanifests%2F0.2.1-SNAPSHOT

Blob created

Fri Apr 20 2018 09:11:26 GMT-0400 (Eastern Daylight Time)

Blob updated

Tue Apr 24 2018 09:27:11 GMT-0400 (Eastern Daylight Time)


  When these images disappear for a while - the pods fail to come up.



  Thank you
  /michael
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] SDC-BE pod started but it's responding with 503 HTTP code

[Tomasz Kapałka]

Hi Roger.

Thanks for the info. Will try to increase the initial delay for now and we will 
see.

BR
Tomasz

From: Roger Maitland 
Sent: wtorek, 24 kwietnia 2018 22:15
To: Tomasz Kapałka ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] SDC-BE pod started but it's responding with 503 
HTTP code

Hi Tomasz,

Sorry I don’t know the details of what the config-backend job is doing.

Note that the SDC team has changed their internal architecture and have 
introduced new containers (splitting the sdc-be container) so things will 
change again once we complete the new Helm charts.

Cheers,
Roger

From: Tomasz Kapałka 
>
Date: Tuesday, April 24, 2018 at 9:49 AM
To: Roger Maitland 
>, 
"onap-discuss@lists.onap.org" 
>
Subject: RE: [onap-discuss] SDC-BE pod started but it's responding with 503 
HTTP code

Hi Roger

Thanks will check this. Could you please let mw know what exactly the 
config-backend pod is doing? As I have reviewed it and it seems that is only to 
make sure that sdc-be pod is running correctly. Am I right?

BR
Tomasz Kapalka

From: Roger Maitland 
>
Sent: wtorek, 24 kwietnia 2018 15:28
To: Tomasz Kapałka 
>; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] SDC-BE pod started but it's responding with 503 
HTTP code

Hi Tomasz,

There is a known problem with how SDC starts up that may cause this problem.  I 
suspect it’s due to a timing problem during startup (the readiness probes 
aren’t waiting long enough for the dev-sdc-be-config-backend job to complete). 
If you’d like to try to solve the problem, try changing the readiness 
‘initialDelaySeconds’ values from 10 seconds to 30 seconds within sdc (if you 
grep you’ll see there are several of them).

Thanks,
Roger

From: 
>
 on behalf of Tomasz Kapałka 
>
Date: Friday, April 20, 2018 at 12:03 PM
To: "onap-discuss@lists.onap.org" 
>
Subject: [onap-discuss] SDC-BE pod started but it's responding with 503 HTTP 
code

Hi


We are trying to start ONAP on GoogleCloud VM/Rancher/Kubernetes. We are using 
cd.sh script provided in https://jira.onap.org/browse/OOM-716 (the latest 
version: [^cd.sh).]

The problem is with SDC-BE pod. It is shown in Kubernetes that it's working 
fine as port 8443 is open but when we try to get this port or 8080 via http we 
got 503 Service Unavailable. Few other pods like dev-sdc-be-config-backend, 
dev-sdc-fe are waiting for this service to respond properly but it's not doing 
that. We have reviewed the logs from sdc-be and there is nothing interesting at 
list from ERROR point of few. Seems that the service is not able to respond 
properly.

Seems that the rest pods are waiting for sdc-be to create web context /sdc2 but 
this is not happening!

Logs from SDC-BE:

https://jira.onap.org/secure/attachment/11445/sdc-be.txt

POD declaration:

https://jira.onap.org/secure/attachment/11447/sdc-be-pod-configuration.yaml

Could you please help?

BR
Tomasz Kapałka
[stopka]
Tomasz Kapałka
Test Automation Programmer | Amartus
www.amartus.com


HQ: 4/5 Burton Hall Park Sandyford Industrial Estate Dublin 18 Ireland | t: 
+353 1 663 80 00

R: ul. Wasilewskiego 20/14 30-305 Kraków Poland | t: +48 12 222 00 18

[cid:image002.png@01D3D890.66BBA4A0]  
[cid:image003.png@01D3D890.66BBA4A0]    
[cid:image004.png@01D3D890.66BBA4A0] 






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] Control Loop Sub Committee Minutes from 4/18/2018

[Stephen Terrill]

Hi Pam,

I suggest that you consider to schedule a presentation to the TSC on latest in 
the control loop subcommittee – I think it would be interesting to get an 
update (actually there is supposed to be a rolling update from the 
sub-committees, this could be the control loop sub-committee).

BR,

Steve

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of DRAGOSH, PAMELA L (PAM)
Sent: Tuesday, April 24, 2018 6:02 PM
To: onap-tsc ; onap-discuss@lists.onap.org
Subject: [onap-tsc] Control Loop Sub Committee Minutes from 4/18/2018

ONAP,

The recording and minutes for the 4/18/2018 Control Loop Sub Committee are 
located here:

https://wiki.onap.org/display/DW/04-18-2018+Control+Loop+Sub+Committee+Weekly+Meeting

Briefly:


  *   Discussion around the current status of Beijing Pairwise Testing. Thank 
you Ron Shachman and Alex Shatov for driving this work.
  *   Discussion around the Casablanca Auto Scale Out Use Case. Thank you to 
Scott Blandford for running this.

I would like to ask the TSC to encourage their team members to help start 
contributing to the committee. It seems the bulk of the work is being done by a 
small core group of folks within AT and our calls for help are not being 
answered by the other folks who are simply listening in on the meeting. There 
are opportunities to help with:


  *   Help defining functional requirements for Casablanca Control Loops
  *   Help with flow diagrams for all the scale out scenarios
  *   Help with defining a Common Actor API to simplify interaction between 
Policy/VID and the controllers.
  *   Help with taking notes/minutes for the meeting calls

Thanks,

Pam Dragosh
ONAP Control Loop Sub Committee Chair

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

Re: [onap-discuss] SDC-BE pod started but it's responding with 503 HTTP code

[Roger Maitland]

Hi Tomasz,

Sorry I don’t know the details of what the config-backend job is doing.

Note that the SDC team has changed their internal architecture and have 
introduced new containers (splitting the sdc-be container) so things will 
change again once we complete the new Helm charts.

Cheers,
Roger

From: Tomasz Kapałka 
Date: Tuesday, April 24, 2018 at 9:49 AM
To: Roger Maitland , "onap-discuss@lists.onap.org" 

Subject: RE: [onap-discuss] SDC-BE pod started but it's responding with 503 
HTTP code

Hi Roger

Thanks will check this. Could you please let mw know what exactly the 
config-backend pod is doing? As I have reviewed it and it seems that is only to 
make sure that sdc-be pod is running correctly. Am I right?

BR
Tomasz Kapalka

From: Roger Maitland 
Sent: wtorek, 24 kwietnia 2018 15:28
To: Tomasz Kapałka ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] SDC-BE pod started but it's responding with 503 
HTTP code

Hi Tomasz,

There is a known problem with how SDC starts up that may cause this problem.  I 
suspect it’s due to a timing problem during startup (the readiness probes 
aren’t waiting long enough for the dev-sdc-be-config-backend job to complete). 
If you’d like to try to solve the problem, try changing the readiness 
‘initialDelaySeconds’ values from 10 seconds to 30 seconds within sdc (if you 
grep you’ll see there are several of them).

Thanks,
Roger

From: 
>
 on behalf of Tomasz Kapałka 
>
Date: Friday, April 20, 2018 at 12:03 PM
To: "onap-discuss@lists.onap.org" 
>
Subject: [onap-discuss] SDC-BE pod started but it's responding with 503 HTTP 
code

Hi


We are trying to start ONAP on GoogleCloud VM/Rancher/Kubernetes. We are using 
cd.sh script provided in https://jira.onap.org/browse/OOM-716 (the latest 
version: [^cd.sh).]

The problem is with SDC-BE pod. It is shown in Kubernetes that it's working 
fine as port 8443 is open but when we try to get this port or 8080 via http we 
got 503 Service Unavailable. Few other pods like dev-sdc-be-config-backend, 
dev-sdc-fe are waiting for this service to respond properly but it's not doing 
that. We have reviewed the logs from sdc-be and there is nothing interesting at 
list from ERROR point of few. Seems that the service is not able to respond 
properly.

Seems that the rest pods are waiting for sdc-be to create web context /sdc2 but 
this is not happening!

Logs from SDC-BE:

https://jira.onap.org/secure/attachment/11445/sdc-be.txt

POD declaration:

https://jira.onap.org/secure/attachment/11447/sdc-be-pod-configuration.yaml

Could you please help?

BR
Tomasz Kapałka
[stopka]
Tomasz Kapałka
Test Automation Programmer | Amartus
www.amartus.com


HQ: 4/5 Burton Hall Park Sandyford Industrial Estate Dublin 18 Ireland | t: 
+353 1 663 80 00

R: ul. Wasilewskiego 20/14 30-305 Kraków Poland | t: +48 12 222 00 18

[cid:image002.png@01D3D890.66BBA4A0]  
[cid:image003.png@01D3D890.66BBA4A0]    
[cid:image004.png@01D3D890.66BBA4A0] 






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

[onap-discuss] AAI weekly call 4/25

[FORSYTH, JAMES]

Hi, All,

Crowdsourcing agenda items for tomorrow’s call:

https://wiki.onap.org/display/DW/2018-04-25+AAI+Weekly+Meeting+Notes+-+open+for+agenda+items

Feel free to add a row at the top if you have a discussion item.

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

Re: [onap-discuss] [oom][sdc] SDC-ES pod not reaching running state

[Mandeep Khinda]

I am having the same issue.  I just raised 
https://jira.onap.org/browse/SDC-1259 to track the resolution.

From:  on behalf of bharath thiruveedula 

Date: Tuesday, April 24, 2018 at 1:31 PM
To: Michael O'Brien , "onap-discuss@lists.onap.org" 
, "david.sauvag...@bell.ca" 

Subject: [onap-discuss] [oom][sdc] SDC-ES pod not reaching running state


Hi ,



I am trying to launch ONAP using OOM master branch. I am facing errors to make 
dev-sdc-es pod in running state. I can see the following error in the log

"FATAL: NoMethodError: undefined method 'each' for "dev-sdc-es.onap": String"



Let me know if you need more info from me.



Best Regards

Bharath T
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] [controlloop] Call for Agenda 4/25/2018 weekly Control Loop Sub Committee meeting

[DRAGOSH, PAMELA L (PAM)]

ONAP,

Please feel free to add to the wiki page:

https://wiki.onap.org/display/DW/04-25-2018+Control+Loop+Sub+Committee+Weekly+Meeting

thanks,

Pam Dragosh
ONAP Control Loop Sub Committee Chair
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [modeling] Patterns of translating IM into TOSCA-based DM

[Katzman, Anatoly]

Hi all,
For your information, there is a new 
page
 in the wiki to discuss best practices for translation of IM into the 
TOSCA-based Internal Data Model for R3.
Your feedback and contributions are welcome.
Regards,
Anatoly Katzman
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [oom][portal] Couldn't make portal-cassandra to be up

[bharath thiruveedula]

Hi OOM team,


I was trying to launch ONAP using OOM master. I am facing following error in 
portal-cassandra.


"Connection error: ('unable to connect to any servers', {'127.0.0.1', 
'Authentication failed('Failed to authenticate to 127.0.0.1: Error from server: 
code 0100 [Bad credentials] message="username and/or password are incorrect",)})

Connection error: ('unable to connect to any servers', {'127.0.0.1',, 
error(111, "Tried connecting to [('127.0.0.1', 9042)]. Last error:connecion 
refused")]"


I enabled policy, consul, message-router, sdc, portal, vid components only.


Am I missing something here?


Best Regards

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

[onap-discuss] [oom][sdc] SDC-ES pod not reaching running state

[bharath thiruveedula]

Hi ,


I am trying to launch ONAP using OOM master branch. I am facing errors to make 
dev-sdc-es pod in running state. I can see the following error in the log

"FATAL: NoMethodError: undefined method 'each' for "dev-sdc-es.onap": String"


Let me know if you need more info from me.


Best Regards

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

Re: [onap-discuss] [sdc] [catalog-be] Changing Log Levels in for CATALOG-BE

[Lando,Michael]

Hi,

I updated the link to explain how to open the logs.











BR,

[Michael Lando]

AT Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
···
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: michael.la...@intl.att.com

From: onap-discuss-boun...@lists.onap.org  
On Behalf Of Satyaki Mallick
Sent: Tuesday, April 24, 2018 18:05
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [sdc] [catalog-be] Changing Log Levels in for CATALOG-BE

Hi,

I want to change the log level to debug or trace.

Checking the ONAP Wiki Page, I found that it is mentioned, where to change the 
log-level, But not how to change it, in this link.
https://wiki.onap.org/display/DW/SDC+Troubleshooting



Can someone help me regarding this?
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Control Loop Sub Committee Minutes from 4/18/2018

[DRAGOSH, PAMELA L (PAM)]

ONAP,

The recording and minutes for the 4/18/2018 Control Loop Sub Committee are 
located here:

https://wiki.onap.org/display/DW/04-18-2018+Control+Loop+Sub+Committee+Weekly+Meeting

Briefly:


· Discussion around the current status of Beijing Pairwise Testing. 
Thank you Ron Shachman and Alex Shatov for driving this work.

· Discussion around the Casablanca Auto Scale Out Use Case. Thank you 
to Scott Blandford for running this.

I would like to ask the TSC to encourage their team members to help start 
contributing to the committee. It seems the bulk of the work is being done by a 
small core group of folks within AT and our calls for help are not being 
answered by the other folks who are simply listening in on the meeting. There 
are opportunities to help with:


· Help defining functional requirements for Casablanca Control Loops

· Help with flow diagrams for all the scale out scenarios

· Help with defining a Common Actor API to simplify interaction between 
Policy/VID and the controllers.

· Help with taking notes/minutes for the meeting calls

Thanks,

Pam Dragosh
ONAP Control Loop Sub Committee Chair

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

[onap-discuss] [integration][oom] Integration Working Session

[Yunxia Chen]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Yunxia Chen:MAILTO:helen.c...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 ss:MAILTO:onap-discuss@lists.onap.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Yang Xu (Y
 ang, Fixed Network)":MAILTO:yang@huawei.com
DESCRIPTION;LANGUAGE=en-US:When: Occurs every Monday\, Tuesday\, Wednesday 
 and Friday from 8:00 AM to 9:00 AM effective 4/23/2018 until 5/23/2018. (U
 TC-08:00) Pacific Time (US & Canada)\nWhere: https://zoom.us/j/44\
 n\n*~*~*~*~*~*~*~*~*~*\n\n\n
RRULE:FREQ=WEEKLY;UNTIL=20180523T15Z;INTERVAL=1;BYDAY=MO,TU,WE,FR;WKST=
 SU
SUMMARY;LANGUAGE=en-US:[integration][oom] Integration Working Session
DTSTART;TZID=Pacific Standard Time:20180423T08
DTEND;TZID=Pacific Standard Time:20180423T09
UID:DB6723D8-86B6-4AEF-B6C9-D5C703B583A5
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180424T151945Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:1
LOCATION;LANGUAGE=en-US:https://zoom.us/j/44
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-OWNERAPPTID:2116336784
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
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [sdc] [catalog-be] Changing Log Levels in for CATALOG-BE

[Satyaki Mallick]

Hi,

I want to change the log level to debug or trace.

Checking the ONAP Wiki Page, I found that it is mentioned, where to change
the log-level, *But* not how to change it, in this link.
https://wiki.onap.org/display/DW/SDC+Troubleshooting



Can someone help me regarding this?
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [modeling] ONAP Resource IM Discussion Apr 27 - Invitation

[yangxu (H)]

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=yangxu (H):MAILTO:yang...@huawei.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=zh-CN:Hi All\,\n\nThis is an invitation for this week
 ’s resource IM discussion call.\n\nMeeting Information:\nMeeting room: h
 ttps://zoom.us/j/9117271979\nTime: Friday 9pm~10pm China\, 9am~10am US Eas
 tern\n\nCurrent Agenda:\n-deprecate legacy HPA related attributes\n\nBR\,\
 nXu\n\n
SUMMARY;LANGUAGE=zh-CN:[onap-discuss][modeling] ONAP Resource IM Discussion
  Apr 27 - Invitation
DTSTART;TZID=W. Australia Standard Time:20180427T21
DTEND;TZID=W. Australia Standard Time:20180427T22
UID:04008200E00074C5B7101A82E008E0ED852D68D2D301000
 01000E61936F491EBDC4EBA8E7B3C5159A54D
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180424T145022Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:4
LOCATION;LANGUAGE=zh-CN:Zoom Id: 9117271979
X-MICROSOFT-CDO-APPT-SEQUENCE:4
X-MICROSOFT-CDO-OWNERAPPTID:-1563670558
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [policy] Call for Agenda 4/25/2018 Policy Bi-Weekly Meeting

[DRAGOSH, PAMELA L (PAM)]

ONAP,

Please use this wiki for any agenda items you wish to discuss:

https://wiki.onap.org/display/DW/04-25-2018+Policy+Bi-Weekly+Meeting

thanks,

Pam Dragosh
ONAP Policy PTL

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

Re: [onap-discuss] SDC-BE pod started but it's responding with 503 HTTP code

[Tomasz Kapałka]

Hi Roger

Thanks will check this. Could you please let mw know what exactly the 
config-backend pod is doing? As I have reviewed it and it seems that is only to 
make sure that sdc-be pod is running correctly. Am I right?

BR
Tomasz Kapalka

From: Roger Maitland 
Sent: wtorek, 24 kwietnia 2018 15:28
To: Tomasz Kapałka ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] SDC-BE pod started but it's responding with 503 
HTTP code

Hi Tomasz,

There is a known problem with how SDC starts up that may cause this problem.  I 
suspect it’s due to a timing problem during startup (the readiness probes 
aren’t waiting long enough for the dev-sdc-be-config-backend job to complete). 
If you’d like to try to solve the problem, try changing the readiness 
‘initialDelaySeconds’ values from 10 seconds to 30 seconds within sdc (if you 
grep you’ll see there are several of them).

Thanks,
Roger

From: 
>
 on behalf of Tomasz Kapałka 
>
Date: Friday, April 20, 2018 at 12:03 PM
To: "onap-discuss@lists.onap.org" 
>
Subject: [onap-discuss] SDC-BE pod started but it's responding with 503 HTTP 
code

Hi


We are trying to start ONAP on GoogleCloud VM/Rancher/Kubernetes. We are using 
cd.sh script provided in https://jira.onap.org/browse/OOM-716 (the latest 
version: [^cd.sh).]

The problem is with SDC-BE pod. It is shown in Kubernetes that it's working 
fine as port 8443 is open but when we try to get this port or 8080 via http we 
got 503 Service Unavailable. Few other pods like dev-sdc-be-config-backend, 
dev-sdc-fe are waiting for this service to respond properly but it's not doing 
that. We have reviewed the logs from sdc-be and there is nothing interesting at 
list from ERROR point of few. Seems that the service is not able to respond 
properly.

Seems that the rest pods are waiting for sdc-be to create web context /sdc2 but 
this is not happening!

Logs from SDC-BE:

https://jira.onap.org/secure/attachment/11445/sdc-be.txt

POD declaration:

https://jira.onap.org/secure/attachment/11447/sdc-be-pod-configuration.yaml

Could you please help?

BR
Tomasz Kapałka
[stopka]
Tomasz Kapałka
Test Automation Programmer | Amartus
www.amartus.com


HQ: 4/5 Burton Hall Park Sandyford Industrial Estate Dublin 18 Ireland | t: 
+353 1 663 80 00

R: ul. Wasilewskiego 20/14 30-305 Kraków Poland | t: +48 12 222 00 18

[cid:image002.png@01D3D890.66BBA4A0]  
[cid:image003.png@01D3D890.66BBA4A0]    
[cid:image004.png@01D3D890.66BBA4A0] 






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] SDC-BE pod started but it's responding with 503 HTTP code

[Roger Maitland]

Hi Tomasz,

There is a known problem with how SDC starts up that may cause this problem.  I 
suspect it’s due to a timing problem during startup (the readiness probes 
aren’t waiting long enough for the dev-sdc-be-config-backend job to complete). 
If you’d like to try to solve the problem, try changing the readiness 
‘initialDelaySeconds’ values from 10 seconds to 30 seconds within sdc (if you 
grep you’ll see there are several of them).

Thanks,
Roger

From:  on behalf of Tomasz Kapałka 

Date: Friday, April 20, 2018 at 12:03 PM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] SDC-BE pod started but it's responding with 503 HTTP 
code

Hi


We are trying to start ONAP on GoogleCloud VM/Rancher/Kubernetes. We are using 
cd.sh script provided in https://jira.onap.org/browse/OOM-716 (the latest 
version: [^cd.sh).]

The problem is with SDC-BE pod. It is shown in Kubernetes that it's working 
fine as port 8443 is open but when we try to get this port or 8080 via http we 
got 503 Service Unavailable. Few other pods like dev-sdc-be-config-backend, 
dev-sdc-fe are waiting for this service to respond properly but it's not doing 
that. We have reviewed the logs from sdc-be and there is nothing interesting at 
list from ERROR point of few. Seems that the service is not able to respond 
properly.

Seems that the rest pods are waiting for sdc-be to create web context /sdc2 but 
this is not happening!

Logs from SDC-BE:

https://jira.onap.org/secure/attachment/11445/sdc-be.txt

POD declaration:

https://jira.onap.org/secure/attachment/11447/sdc-be-pod-configuration.yaml

Could you please help?

BR
Tomasz Kapałka
[stopka]
Tomasz Kapałka
Test Automation Programmer | Amartus
www.amartus.com


HQ: 4/5 Burton Hall Park Sandyford Industrial Estate Dublin 18 Ireland | t: 
+353 1 663 80 00

R: ul. Wasilewskiego 20/14 30-305 Kraków Poland | t: +48 12 222 00 18

[cid:image002.png@01D3D890.66BBA4A0]  
[cid:image003.png@01D3D890.66BBA4A0]    
[cid:image004.png@01D3D890.66BBA4A0] 






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] ONAP subcommittees - reminder.

[GILBERT, MAZIN E (MAZIN E)]

Team, 

The TSC has approved a number of subcommittees in the past. I would like to 
encourage each 
subcommittee chair to share updates with the TSC on a regular basis - either 
through email or
at the TSC Thursday meetings. It is important that the TSC is knowledgable and 
agree of the workplan of the 
subcommittees. Each subcommittee should plan to provide a readout about once a 
month to the TSC.

thanks
mazin


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

Re: [onap-discuss] Beijing SDC deployment is broken

[Lando,Michael]

Hi,

We update our deployment but the job responsible for the docker creation failed.
https://jenkins.onap.org/view/sdc/job/sdc-master-sdc-merge-java/

a fix is in the pipeline once job 948 will complete you will have the docker in 
nexus.

Please validate that the template.json and the docker run you are using is 
aligned to the one in master









BR,

[Michael Lando]

AT Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
···
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: michael.la...@intl.att.com

From: Nemeth, Denes (Nokia - HU/Budapest) 
Sent: Tuesday, April 24, 2018 15:01
To: onap-discuss ; Lando,Michael 

Subject: Beijing SDC deployment is broken


Hi



Can someone help how to deploy SDC with Heat?



SDC deployment scripts searches for an image with sdc-onboard-cassandra-init 
name,

but there is no image like this in



https://nexus3.onap.org/#browse/search/docker=attributes.docker.imageName%3Donap%2Fsdc-onboard-cassandra-init



This is used from /opt/sdc/sdc-os-chef/scripts/docker_run.sh



#Onboard Cassandra-init

function sdc-cs-onboard-init {

echo "docker run sdc-cs-onboard-init..."

if [ ${LOCAL} = false ]; then

docker pull ${PREFIX}/sdc-onboard-cassandra-init:${RELEASE}

fi

Yesterday it was able to start, but had to redeploy because it SDC was not able 
to accept VNF in testing phase.

I think this commit broke the deployment 
https://gerrit.onap.org/r/gitweb?p=sdc.git;a=commit;h=c175a0de2f05d37c1c774684318a525eb96bb59b


Thanks Denes



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

Re: [onap-discuss] [oom][integration] Known issue for integration testing with OOM deployment

[Roger Maitland]

Hi Helen,

Champ and Sparky are new AAI micro-services and are not required for any of the 
existing use cases.  It needs to be fixed but is less urgent.

The portal problem is within the portal project as far as we can tell.  It’s 
trying to communicate internally and failing due to invalid credentials on 
Cassandra.  I’ve been in communication with the portal team on this and I’m 
waiting on a fix.

Cheers,
Roger

From: Yunxia Chen 
Date: Monday, April 23, 2018 at 8:04 PM
To: onap-discuss , Roger Maitland 
, David Sauvageau , Jimmy 
Forsyth 
Subject: Re: [oom][integration] Known issue for integration testing with OOM 
deployment

However, A passed the health check even with those two containers are not up.

Regards,

Helen Chen

From: Helen Chen 00725961 
Date: Monday, April 23, 2018 at 4:34 PM
To: onap-discuss , Roger Maitland 
, "Sauvageau, David" 
Subject: [oom][integration] Known issue for integration testing with OOM 
deployment

Hi, David and Roger,

Do we have anywhere to list all the known issues for integration testing with 
OOM deployment? I know DCAE is not there yet, however, I still get the 
following “CrashLoopBackOff” error on deployment:

dev-aai-champ- :
dev-aai-sparky-be-..:
dev-portal-cassandra-…

Any workaround for it?  I am on Integration-SB-00, freshly installed this 
morning.

Regards,
Helen Chen


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] Beijing SDC deployment is broken

[Nemeth, Denes (Nokia - HU/Budapest)]

Hi



Can someone help how to deploy SDC with Heat?



SDC deployment scripts searches for an image with sdc-onboard-cassandra-init 
name,

but there is no image like this in



https://nexus3.onap.org/#browse/search/docker=attributes.docker.imageName%3Donap%2Fsdc-onboard-cassandra-init



This is used from /opt/sdc/sdc-os-chef/scripts/docker_run.sh



#Onboard Cassandra-init

function sdc-cs-onboard-init {

echo "docker run sdc-cs-onboard-init..."

if [ ${LOCAL} = false ]; then

docker pull ${PREFIX}/sdc-onboard-cassandra-init:${RELEASE}

fi

Yesterday it was able to start, but had to redeploy because it SDC was not able 
to accept VNF in testing phase.

I think this commit broke the deployment 
https://gerrit.onap.org/r/gitweb?p=sdc.git;a=commit;h=c175a0de2f05d37c1c774684318a525eb96bb59b


Thanks Denes



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

Re: [onap-discuss] AAI inventory update after onboarding / instantiation on openstack using SO API

[SMOKOWSKI, STEVEN]

A does not support a name value pair paradigm, however the schema/api’s are 
easily updated via modifying the oxml file.

Thanks

-Steve

From: Ullas Kumar Kotrappa Yereseemi 
Date: Tuesday, April 24, 2018 at 2:53 AM
To: "SMOKOWSKI, STEVEN" , "FORSYTH, JAMES" , 
"onap-discuss@lists.onap.org" 
Cc: Syed Atif Husain 
Subject: RE: [onap-discuss] AAI inventory update after onboarding / 
instantiation on openstack using SO API

Hello All,

Is there any option of adding additional data into A against an instantiated 
VNF. It can be in the form of Name Value pairs . Please let us know if any such 
options are available.

Regards,
Ullas


From: SMOKOWSKI, STEVEN [mailto:ss8...@att.com]
Sent: Friday, April 13, 2018 12:39 AM
To: Ullas Kumar Kotrappa Yereseemi ; FORSYTH, JAMES 
; onap-discuss@lists.onap.org
Cc: Syed Atif Husain 
Subject: Re: [onap-discuss] AAI inventory update after onboarding / 
instantiation on openstack using SO API

Not all heat outputs are generically added to A  I believe only stack-id is 
today.  SDNC does write some data in terms of ip-addresses though.  I would 
check with them, or A  I cannot answer this from SO.  I do know we have 
thought about adding those generic outputs.

Thanks

-Steve

From: Ullas Kumar Kotrappa Yereseemi 
>
Date: Thursday, April 12, 2018 at 2:39 PM
To: "FORSYTH, JAMES" >, "SMOKOWSKI, 
STEVEN" >, 
"onap-discuss@lists.onap.org" 
>
Cc: Syed Atif Husain >
Subject: RE: [onap-discuss] AAI inventory update after onboarding / 
instantiation on openstack using SO API

Hello All,

As part of the SO API VNF Module creation, there is an async process .

POST 
/mso/WorkflowMessage/VNFAResponse/939ba1f2-67c5-417b-803f-80fdf5289b8c-1522947354911



vVerifier_name
Ex-vice_4_5_2018_VNF_MODULE_V1-vVerifier-32wmuzerbmk4


vVerifier_ip
10.50.1.107



Can see the IP address of the VNF which was instantiated (below snapshot 
collected via TCP DUMPS) , but cannot get this information from AAI. Does this 
response gets added to AAI against VNF instance ? if so how can we get this?

Also have tried named queries but did not get IP address of the instance.

[cid:image001.png@01D3D2BB.97D851D0]

Regards,
Ullas
Desk: +91 82141 89692
Mobile: +91 7338633314


From: Ullas Kumar Kotrappa Yereseemi
Sent: Friday, April 6, 2018 4:08 PM
To: FORSYTH, JAMES >; SMOKOWSKI, STEVEN 
>; 
onap-discuss@lists.onap.org
Cc: Syed Atif Husain >
Subject: RE: [onap-discuss] AAI inventory update after onboarding / 
instantiation on openstack using SO API

Hello Jimmy,

Thanks for the details , that did gave some more information but still the 
information on the Host and IP of the VNF was not available as part of the AAI 
Call ( I tried the depth 3 and greater than 3 as well) . As part of the VNF 
Module Initialization call via SO.

http://{ONAP_MSO}ecomp/mso/infra/serviceInstances/v4/{instance_id}/vnfs/{VNF_ID}vfModules

The response for the above call for VNF creation was the instance ID. How can 
we get what information updated to AAI as part of the VNF Module creation API 
call.

Regards,
Ullas

From: FORSYTH, JAMES [mailto:jf2...@att.com]
Sent: Thursday, April 5, 2018 9:32 PM
To: Ullas Kumar Kotrappa Yereseemi 
>; SMOKOWSKI, STEVEN 
>; 
onap-discuss@lists.onap.org
Cc: Syed Atif Husain >
Subject: Re: [onap-discuss] AAI inventory update after onboarding / 

Re: [onap-discuss] UUI/VID Discussion

[Lingli Deng]

Thank you Lior.

Regarding S3P and change management support, Tao will provider an update
shortly.

 

Lingli

 

From: Nachmias, Lior  
Sent: 2018年4月24日 16:34
To: shentao ; Lefevre, Catherine
; Sonsino, Ofir ; Lingli Deng
; onap-discuss 
Cc: Lefevre, Catherine 
Subject: RE: UUI/VID Discussion

 

Good day,

 

We (UUI and VID project teams) had a call this morning to discuss how we can
define a new project that will combine VID/UUI current functionalities, in
order to optimize the effort by combining our team members.

 

Presentation and meeting notes are attached. 

 

Thanks,

Lior Nachmias

 

 

AT Network Application Development ・ NetCom  

Tel Aviv | Tampa | Atlanta | New Jersey |Chicago

・・
・

Office: +972 (3) 9767757

 

-Original Appointment-
From: shentao [mailto:shen...@chinamobile.com] 
Sent: Monday, April 23, 2018 5:57 AM
To: shentao; Lefevre, Catherine; Sonsino, Ofir; Nachmias, Lior; Lingli Deng
Subject: UUI/VID Discussion
When: Tuesday, April 24, 2018 9:30 AM-10:30 AM (UTC+02:00) Athens,
Bucharest.
Where: https://zoom.us/j/651540147

 

 

时间: 2018年4月24日星期二 14:30-15:30(UTC+08:00) 北京，重庆，香港特别行政
区，乌鲁木齐。

地点:   https://zoom.us/j/651540147

 

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

 

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

Re: [onap-discuss] [sdc][integration] SDC tester page hangs when clicking on Accept button

[Nemeth, Denes (Nokia - HU/Budapest)]

Hi

This has been merged into master. Does anyone know how to check if it has been 
included in the SDC docker images too?

D.

From:  on behalf of "Yang Xu (Yang, Fixed 
Network)" 
Date: 2018. April 24., Tuesday 2:17
To: "Lando,Michael" , onap-discuss 

Subject: Re: [onap-discuss] [sdc][integration] SDC tester page hangs when 
clicking on Accept button

Michael,

Thanks for the quick fix which solved the issue. I have closed the JIRA.

Regards,
-Yang

From: Lando,Michael [mailto:ml6...@intl.att.com]
Sent: Monday, April 23, 2018 11:39 AM
To: Yang Xu (Yang, Fixed Network); onap-discuss
Subject: RE: [sdc][integration] SDC tester page hangs when clicking on Accept 
button

Hi,

We are aware of this issue a fix is being pushed now.

I will update once the docker with the fix is available.









BR,

[Michael Lando]

AT Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
···
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: michael.la...@intl.att.com

From: Yang Xu (Yang, Fixed Network) 
Sent: Monday, April 23, 2018 18:12
To: Lando,Michael ; onap-discuss 

Subject: [sdc][integration] SDC tester page hangs when clicking on Accept button

Dear Michael,

We are doing VoLTE VNF onboarding test in integration lab with HEAT 
installation, and see tester page hangs when clicking on Accept button. This 
issue blocks all other VoLTE tests. Could you fix it quickly or give a 
workaround? You can take a look at  Integration-SB-03 env. The JIRA ticket is 
https://jira.onap.org/browse/SDC-1247.

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

Re: [onap-discuss] UUI/VID Discussion

[Sonsino, Ofir]

Also available in ONAP wiki:
https://wiki.onap.org/pages/viewpage.action?pageId=29788612

Thanks,
Ofir

_
From: Nachmias, Lior
Sent: Tuesday, April 24, 2018 11:34 AM
To: shentao ; Lefevre, Catherine 
; Sonsino, Ofir ; Lingli Deng 
; onap-discuss 
Cc: Lefevre, Catherine 
Subject: RE: UUI/VID Discussion


Good day,

We (UUI and VID project teams) had a call this morning to discuss how we can 
define a new project that will combine VID/UUI current functionalities, in 
order to optimize the effort by combining our team members.

Presentation and meeting notes are attached.

Thanks,
Lior Nachmias

 << File: VID and UUI Discussion.pptx >>

AT Network Application Development ・ NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
・・・
Office: +972 (3) 9767757

-Original Appointment-
From: shentao [mailto:shen...@chinamobile.com]
Sent: Monday, April 23, 2018 5:57 AM
To: shentao; Lefevre, Catherine; Sonsino, Ofir; Nachmias, Lior; Lingli Deng
Subject: UUI/VID Discussion
When: Tuesday, April 24, 2018 9:30 AM-10:30 AM (UTC+02:00) Athens, Bucharest.
Where: https://zoom.us/j/651540147


时间: 2018年4月24日星期二 14:30-15:30(UTC+08:00) 北京，重庆，香港特别行政区，乌鲁木齐。

地点: https://zoom.us/j/651540147

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


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

Re: [onap-discuss] AAI inventory update after onboarding / instantiation on openstack using SO API

[Ullas Kumar Kotrappa Yereseemi]

Hello All,

Is there any option of adding additional data into A against an instantiated 
VNF. It can be in the form of Name Value pairs . Please let us know if any such 
options are available.

Regards,
Ullas


From: SMOKOWSKI, STEVEN [mailto:ss8...@att.com]
Sent: Friday, April 13, 2018 12:39 AM
To: Ullas Kumar Kotrappa Yereseemi ; FORSYTH, JAMES 
; onap-discuss@lists.onap.org
Cc: Syed Atif Husain 
Subject: Re: [onap-discuss] AAI inventory update after onboarding / 
instantiation on openstack using SO API

Not all heat outputs are generically added to A  I believe only stack-id is 
today.  SDNC does write some data in terms of ip-addresses though.  I would 
check with them, or A  I cannot answer this from SO.  I do know we have 
thought about adding those generic outputs.

Thanks

-Steve

From: Ullas Kumar Kotrappa Yereseemi 
>
Date: Thursday, April 12, 2018 at 2:39 PM
To: "FORSYTH, JAMES" >, "SMOKOWSKI, 
STEVEN" >, 
"onap-discuss@lists.onap.org" 
>
Cc: Syed Atif Husain >
Subject: RE: [onap-discuss] AAI inventory update after onboarding / 
instantiation on openstack using SO API

Hello All,

As part of the SO API VNF Module creation, there is an async process .

POST 
/mso/WorkflowMessage/VNFAResponse/939ba1f2-67c5-417b-803f-80fdf5289b8c-1522947354911



vVerifier_name
Ex-vice_4_5_2018_VNF_MODULE_V1-vVerifier-32wmuzerbmk4


vVerifier_ip
10.50.1.107



Can see the IP address of the VNF which was instantiated (below snapshot 
collected via TCP DUMPS) , but cannot get this information from AAI. Does this 
response gets added to AAI against VNF instance ? if so how can we get this?

Also have tried named queries but did not get IP address of the instance.

[cid:image001.png@01D3D2BB.97D851D0]

Regards,
Ullas
Desk: +91 82141 89692
Mobile: +91 7338633314


From: Ullas Kumar Kotrappa Yereseemi
Sent: Friday, April 6, 2018 4:08 PM
To: FORSYTH, JAMES >; SMOKOWSKI, STEVEN 
>; 
onap-discuss@lists.onap.org
Cc: Syed Atif Husain >
Subject: RE: [onap-discuss] AAI inventory update after onboarding / 
instantiation on openstack using SO API

Hello Jimmy,

Thanks for the details , that did gave some more information but still the 
information on the Host and IP of the VNF was not available as part of the AAI 
Call ( I tried the depth 3 and greater than 3 as well) . As part of the VNF 
Module Initialization call via SO.

http://{ONAP_MSO}ecomp/mso/infra/serviceInstances/v4/{instance_id}/vnfs/{VNF_ID}vfModules

The response for the above call for VNF creation was the instance ID. How can 
we get what information updated to AAI as part of the VNF Module creation API 
call.

Regards,
Ullas

From: FORSYTH, JAMES [mailto:jf2...@att.com]
Sent: Thursday, April 5, 2018 9:32 PM
To: Ullas Kumar Kotrappa Yereseemi 
>; SMOKOWSKI, STEVEN 
>; 
onap-discuss@lists.onap.org
Cc: Syed Atif Husain >
Subject: Re: [onap-discuss] AAI inventory update after onboarding / 
instantiation on openstack using SO API

Hi, Ullas,

If you want to see objects that are contained by the vnf, I suggest setting the 
depth= query parameter.  By default depth is set to 0, meaning only fetch the 
given object and not objects that it contains.

Example: