[onap-discuss] [devops] nexus3 throughput retest

[Michael O'Brien]

Team,
   Passed to LF.
Posted my latest test to the end of OOM-933
https://jira.onap.org/browse/OOM-933

Quoting here
Fast overall but issues with pauses still.



NExus3 jvm retrofit of heap from 1.2 to 6g testing on 128g 32vCore azure vm 
docker 17.03 10G network

Dont think it is the JVM unless I see the heap stats - and the cpu spike on GC 
collection
check the thread pool size and the open file setting (Gary) to start

25 min download of 90 containers is normal - but with pausing behavior (single 
vm not 2 like last time)
still seeing slowdown 5 min in - with bursts - but no full pause for 30-60 like 
before
around 12 min seeing 5 second thread blocks ever 15 sec when 50 of 90 left

1  sudo curl https://releases.rancher.com/install-docker/17.03.sh | sh

2  sudo usermod -aG docker ubuntu

./prepull_docker_master.sh



times are 2 min apart - numbers are remaining docker image pulls



Last login: Fri May  4 19:22:04 2018 from 173.32.179.153

ubuntu@a-onap-auto-20180503-0:~$ sudo ps -ef | grep docker | grep pull | wc -l

79

ubuntu@a-onap-auto-20180503-0:~$ 1522

ubuntu@a-onap-auto-20180503-0:~$ sudo ps -ef | grep docker | grep pull | wc -l

77

ubuntu@a-onap-auto-20180503-0:~$ 1524

ubuntu@a-onap-auto-20180503-0:~$ sudo ps -ef | grep docker | grep pull | wc -l

73

ubuntu@a-onap-auto-20180503-0:~$ 1526

ubuntu@a-onap-auto-20180503-0:~$ sudo ps -ef | grep docker | grep pull | wc -l

71

ubuntu@a-onap-auto-20180503-0:~$ 1528

ubuntu@a-onap-auto-20180503-0:~$ sudo ps -ef | grep docker | grep pull | wc -l

66

ubuntu@a-onap-auto-20180503-0:~$ 1530

ubuntu@a-onap-auto-20180503-0:~$ sudo ps -ef | grep docker | grep pull | wc -l

59

ubuntu@a-onap-auto-20180503-0:~$ 1532



ee5c7445b360: Downloading [>  ] 
161.7 MB/329.7 MB

ee5c7445b360: Downloading [>  ] 
164.4 MB/329.7 MB

ee5c7445b360: Downloading [=> ] 
168.1 MB/329.7 MB

ee5c7445b360: Downloading [=> ] 
197.4 MB/329.7 MB

above 10 sec apart



ubuntu@a-onap-auto-20180503-0:~$ sudo ps -ef | grep docker | grep pull | wc -l

50

ubuntu@a-onap-auto-20180503-0:~$ 1534

ubuntu@a-onap-auto-20180503-0:~$ sudo ps -ef | grep docker | grep pull | wc -l

40

ubuntu@a-onap-auto-20180503-0:~$ 1536



15 sec thread blocks - every 20 sec

speed back up now

ubuntu@a-onap-auto-20180503-0:~$ sudo ps -ef | grep docker | grep pull | wc -l

37

ubuntu@a-onap-auto-20180503-0:~$ 1538

ubuntu@a-onap-auto-20180503-0:~$ sudo ps -ef | grep docker | grep pull | wc -l

32

ubuntu@a-onap-auto-20180503-0:~$ 1540

ubuntu@a-onap-auto-20180503-0:~$ sudo ps -ef | grep docker | grep pull | wc -l

23

ubuntu@a-onap-auto-20180503-0:~$ 1542

ubuntu@a-onap-auto-20180503-0:~$ sudo ps -ef | grep docker | grep pull | wc -l

17

ubuntu@a-onap-auto-20180503-0:~$ 1544

current speed

d652b8d9672e: Downloading [=> ] 
204.9 MB/577 MB

d652b8d9672e: Downloading [=> ] 
293.9 MB/577 MB

d652b8d9672e: Downloading [=> ] 
389.2 MB/577 MB

d652b8d9672e: Downloading [=> ] 
433.9 MB/577 MB

d652b8d9672e: Downloading [===>   ] 
502.4 MB/577 MB

above 10 sec apart



ubuntu@a-onap-auto-20180503-0:~$ 1544

ubuntu@a-onap-auto-20180503-0:~$ sudo ps -ef | grep docker | grep pull | wc -l

7

ubuntu@a-onap-auto-20180503-0:~$ 1546

ubuntu@a-onap-auto-20180503-0:~$ sudo ps -ef | grep docker | grep pull | wc -l

2

ubuntu@a-onap-auto-20180503-0:~$ 1547

ubuntu@a-onap-auto-20180503-0:~$ sudo ps -ef | grep docker | grep pull | wc -l

1

ubuntu@a-onap-auto-20180503-0:~$ 1548

ubuntu@a-onap-auto-20180503-0:~$ sudo ps -ef | grep docker | grep pull | wc -l

0

/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] DCAE deployment in R2 (oom or heat)

[JI, LUSHENG (LUSHENG)]

In our experience, this is likely due to the deployment of this particular 
component, dep-config-binding-service-7b9cfb76b8-l75mp, timed out.
And this is usually due to docker image pulling taking too long.  We are 
working on a work around for this in the DCAE bootstrap container, ETA EoB 
today.

In the meanwhile, if you could prepull images before starting helm install, you 
could try to run the helm install with an additional parameter to override the 
default (which is alway pull), something like this:
helm install local/onap -n dev --namespace onap --set 
global.pullPolicy=IfNotPresent
to avoid pulling images...

There is a job, called dcae-bootstrap, that deploys these 8 pods.  You can 
check its logs for details.  Because it is a job, the pod is gone once it is 
done.  You may have to use -a to see it.

Lusheng


On May 4, 2018, at 3:40 PM, Michal Ptacek 
mailto:m.pta...@partner.samsung.com>> wrote:

Thanks Lusheng for your hints,
I see some trace of dcae now, but it's in "Error syncing pod" state
dcae  dep-config-binding-service-7b9cfb76b8-l75mp0/2   
ContainerCreating   0  6h
need to troubleshoot this further 



Michal
- Original Message -
Sender : JI, LUSHENG (LUSHENG) 
mailto:l...@research.att.com>>
Date : 2018-05-04 19:36 (GMT+1)
Title : Re: [onap-discuss] DCAE deployment in R2 (oom or heat)
To : Michal 
Ptacekmailto:m.pta...@partner.samsung.com>>
CC : nullmailto:onap-discuss@lists.onap.org>>



Michal,



When the DCAE is fully deployed by OOM, there should be 8 additional pods 
deployed.  They may be under a different namespace “dcae”, depends on 
configuration.  You may check it out in place, for example the 
Integration-Jenkins tenant of Intel/Windriver lab.



Moreover, additional components can be deployed at operation time by CLAMP.



Lusheng





On May 4, 2018, at 10:03 AM, Michal Ptacek 
mailto:m.pta...@partner.samsung.com>> wrote:
Hi,



will it be possible to fully deploy DCAE using OOM in R2 ?



It seems that trend is to move to containers from VM's, also DCAE is going into 
this direction.
what I heard here 
https://wiki.onap.org/display/DW/Meetings?preview=/13598723/31982711/dcae-weekly-20180503.mp4
is that currently DCAE can be spawned on single bootstrap VM (8G-16G of RAM) 
and all components are running as docker containers, also it
should be possible to deploy it fully using OOM.
I tried today to deploy latest ONAP in OOM (multinode, single node is not 
possible anymore with 110 pods per k8s host limitation) but I see just 
following dcae pods 



onap  beijing-dcae-cloudify-manager-fb9f5d6bd-bss2n  1/1   
Running 0  4h
onap  beijing-dcae-db-0  1/1   
Running 0  4h
onap  beijing-dcae-db-1  1/1   
Running 0  2h
onap  beijing-dcae-healthcheck-78999885d5-5hts8  1/1   
Running 0  4h
onap  beijing-dcae-redis-0   1/1   
Running 0  4h
onap  beijing-dcae-redis-1   1/1   
Running 0  3h
onap  beijing-dcae-redis-2   1/1   
Running 0  2h
onap  beijing-dcae-redis-3   1/1   
Running 0  2h
onap  beijing-dcae-redis-4   1/1   
Running 0  2h
onap  beijing-dcae-redis-5   1/1   
Running 0  1h





where is the rest ?
please advise



have a nice weekend
thanks,
Michal



___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=qiKb3LQBLje9oy8MjG3MEx1ia4mIocif7RoUY8WQWV8&m=SfX1Jew16Goa7zdY46mVmCqWmV94u9SoqB-0vskjXi0&s=5U2AVfg95KozM5YSXorQ-G-l2rTeDt3psYlLwZ-9eok&e=











 


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

Re: [onap-discuss] DCAE deployment in R2 (oom or heat)

[Michal Ptacek]

Thanks Lusheng for your hints,
I see some trace of dcae now, but it's in "Error syncing pod" state
dcae  dep-config-binding-service-7b9cfb76b8-l75mp    0/2   ContainerCreating   0  6h 
need to troubleshoot this further 
 
Michal
- Original Message -
Sender : JI, LUSHENG  (LUSHENG) 
Date   : 2018-05-04 19:36 (GMT+1)
Title  : Re: [onap-discuss]  DCAE deployment in R2 (oom or heat)
To : Michal Ptacek
CC : null
 



Michal,

 
When the DCAE is fully deployed by OOM, there should be 8 additional pods deployed.  They may be under a different namespace “dcae”, depends on configuration.  You may check it out in place, for example the Integration-Jenkins tenant of Intel/Windriver
 lab.
 
Moreover, additional components can be deployed at operation time by CLAMP. 
 
Lusheng
 
 
On May 4, 2018, at 10:03 AM, Michal Ptacek  wrote:

Hi,

 

will it be possible to fully deploy DCAE using OOM in R2 ?

 

It seems that trend is to move to containers from VM's, also DCAE is going into this direction.

what I heard here https://wiki.onap.org/display/DW/Meetings?preview=/13598723/31982711/dcae-weekly-20180503.mp4

is that currently DCAE can be spawned on single bootstrap VM (8G-16G of RAM) and all components are running as docker containers, also it

should be possible to deploy it fully using OOM.

I tried today to deploy latest ONAP in OOM (multinode, single node is not possible anymore with 110 pods per k8s host limitation) but I see just following dcae pods 

 
onap  beijing-dcae-cloudify-manager-fb9f5d6bd-bss2n  1/1   Running 0  4honap  beijing-dcae-db-0  1/1   Running 0  4honap  beijing-dcae-db-1  1/1   Running 0  2honap  beijing-dcae-healthcheck-78999885d5-5hts8  1/1   Running 0  4honap  beijing-dcae-redis-0   1/1   Running 0  4honap  beijing-dcae-redis-1   1/1   Running 0  3honap  beijing-dcae-redis-2   1/1   Running 0  2honap  beijing-dcae-redis-3   1/1   Running 0  2honap  beijing-dcae-redis-4   1/1   Running 0  2honap  beijing-dcae-redis-5   1/1   Running 0  1h 
 

 

where is the rest ?

please advise

 

have a nice weekend

thanks,

Michal
 
___onap-discuss
 mailing listonap-discuss@lists.onap.orghttps://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=qiKb3LQBLje9oy8MjG3MEx1ia4mIocif7RoUY8WQWV8&m=SfX1Jew16Goa7zdY46mVmCqWmV94u9SoqB-0vskjXi0&s=5U2AVfg95KozM5YSXorQ-G-l2rTeDt3psYlLwZ-9eok&e=
 
 
 
  

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

Re: [onap-discuss] [app-c] Ansible Server details in appc.properties file

[CHO, TAKAMUNE]

On the same directory in APPC docker. You would see the 
appc_southbound.properties file instead. The format for ansible server in 
southbound properties is below:

.ANSIBLE..user
.ANSIBLE..port
.ANSIBLE..password
.ANSIBLE..url

 has to be matched with vnf-type in A&AI.
For example:

vUSP-vCOM.ANSIBLE.HealthCheck.user = XXX
vUSP-vCOM.ANSIBLE.HealthCheck.port = 5000
vUSP-vCOM.ANSIBLE.HealthCheck.password = ABCDEF
vUSP-vCOM.ANSIBLE.HealthCheck.url = https://:5000

In Casablanca release, these ansible server configures will be moving to 
device_authentication table in  maria (now is mysql) db.

Taka

From: ANUMANENI, VENKATA RAMANA
Sent: Friday, May 04, 2018 1:28 PM
To: CHO, TAKAMUNE ; Akula, Ramanjaneyul Reddy (Nokia - 
US/Irving) ; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [app-c] Ansible Server details in appc.properties 
file

Hello APPC team,

I am trying to update Ansible Server details in APPC properties file. But, we 
couldn't find exact parameter to be updated. Could you please provide sample 
appc.properties file which has Ansible Server details?

ariable Name

Description

Type

Comments

User

Username to logon to Ansible Server

Mandatory

Should be provided by APPC.

Password

Password to logon to Ansible Server

Mandatory

Should be provided by APPC.

AgentUrl

The complete URL of the Ansible Server to post the request for execution and 
retrieve results (if in synchronous mode)




Regards
Venkat


From: CHO, TAKAMUNE [mailto:tc0...@att.com]
Sent: Wednesday, April 04, 2018 3:56 PM
To: Akula, Ramanjaneyul Reddy (Nokia - US/Irving) 
mailto:ramanjaneyul_reddy.ak...@nokia.com>>;
 onap-discuss@lists.onap.org
Cc: Anumaneni, Venkataramana (Nokia - US/Irving) 
mailto:venkataraman...@nokia.com>>
Subject: RE: [onap-discuss] [app-c] appc client library location

HI Ramu,

Thanks for interested on APPC.

It sounds like your local_setting.xml for mvn build has an issue, can you 
attach your local_setting to me, I can take a look.

Thanks

Taka

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Akula, Ramanjaneyul 
Reddy (Nokia - US/Irving)
Sent: Wednesday, April 04, 2018 3:27 PM
To: onap-discuss@lists.onap.org
Cc: ANUMANENI, VENKATA RAMANA 
mailto:venkataraman...@nokia.com>>
Subject: [onap-discuss] [app-c] appc client library location

Hi APPC Team,
We are planning to do some VNF configuration using APP-C. For the same, learned 
that we can use the APP-C client libraries (org.onap.appc.client:client-kit, 
org.onap.appc.client:client-lib) to send the LCM request to DMaaP topic 
(http://onap.readthedocs.io/en/latest/submodules/appc.git/docs/APPC%20Client%20Library%20Guide/APPC%20Client%20Library%20Guide.html#appc-client-library

However, we failed to located the needed jars.
Then tried to compile the code using the instructions @ 
"https://wiki.onap.org/display/DW/Building+Entire+ONAP"

While comping the APP-C code, getting below error:

[FATAL] Non-resolvable parent POM for org.onap.appc:appc:1.3.0-SNAPSHOT: 
Failure to find org.onap.ccsdk.parent:odlparent-carbon-sr1:pom:0.1.0 in 
https://repo.maven.apache.org/maven2
 was cached in the local repository, resolution will not be reattempted until 
the update interval of central has elapsed or updates are forced and 
'parent.relativePath' points at wrong local POM @ line 25, column 13
@

Can someone help me on how to get around this problem.


Thanks & best regards,
Ramu




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

[onap-discuss] [ONAP Helpdesk #55626] Gerrit is down

[Jessica Wagantall via RT]

Dear team, 

we are back on track now.. 

Everything is working .

thanks!
Jess

On Fri May 04 14:22:29 2018, jconway wrote:
> Hello,
> We are experiencing an issue with our edge firewalls, you can follow
> the incident here
> 
> https://status.linuxfoundation.org/incidents/zjkddd9wt0yt
> 
> Sorry for any inconvenience.
> 
> Best regards,
> Jordan Conway



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

Re: [onap-discuss] DCAE deployment in R2 (oom or heat)

[JI, LUSHENG (LUSHENG)]

Michal,

When the DCAE is fully deployed by OOM, there should be 8 additional pods 
deployed.  They may be under a different namespace “dcae”, depends on 
configuration.  You may check it out in place, for example the 
Integration-Jenkins tenant of Intel/Windriver lab.

Moreover, additional components can be deployed at operation time by CLAMP.

Lusheng


On May 4, 2018, at 10:03 AM, Michal Ptacek 
mailto:m.pta...@partner.samsung.com>> wrote:

Hi,



will it be possible to fully deploy DCAE using OOM in R2 ?



It seems that trend is to move to containers from VM's, also DCAE is going into 
this direction.
what I heard here 
https://wiki.onap.org/display/DW/Meetings?preview=/13598723/31982711/dcae-weekly-20180503.mp4
is that currently DCAE can be spawned on single bootstrap VM (8G-16G of RAM) 
and all components are running as docker containers, also it
should be possible to deploy it fully using OOM.
I tried today to deploy latest ONAP in OOM (multinode, single node is not 
possible anymore with 110 pods per k8s host limitation) but I see just 
following dcae pods 



onap  beijing-dcae-cloudify-manager-fb9f5d6bd-bss2n  1/1   
Running 0  4h
onap  beijing-dcae-db-0  1/1   
Running 0  4h
onap  beijing-dcae-db-1  1/1   
Running 0  2h
onap  beijing-dcae-healthcheck-78999885d5-5hts8  1/1   
Running 0  4h
onap  beijing-dcae-redis-0   1/1   
Running 0  4h
onap  beijing-dcae-redis-1   1/1   
Running 0  3h
onap  beijing-dcae-redis-2   1/1   
Running 0  2h
onap  beijing-dcae-redis-3   1/1   
Running 0  2h
onap  beijing-dcae-redis-4   1/1   
Running 0  2h
onap  beijing-dcae-redis-5   1/1   
Running 0  1h



where is the rest ?
please advise



have a nice weekend
thanks,
Michal




 

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=qiKb3LQBLje9oy8MjG3MEx1ia4mIocif7RoUY8WQWV8&m=SfX1Jew16Goa7zdY46mVmCqWmV94u9SoqB-0vskjXi0&s=5U2AVfg95KozM5YSXorQ-G-l2rTeDt3psYlLwZ-9eok&e=

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

[onap-discuss] [ONAP Helpdesk #55626] Gerrit is down

[Jordan Conway via RT]

Hello,
We are experiencing an issue with our edge firewalls, you can follow the 
incident here

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

Sorry for any inconvenience.

Best regards,
Jordan Conway
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Gerrit is down

[Gildas Lanilis]

Wiki is down too.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gary Wu
Sent: Friday, May 04, 2018 11:13 AM
To: helpd...@onap.org; onap-discuss 
Subject: [onap-discuss] Gerrit is down

Hi Helpdesk,

gerrit.onap.org is down.  Can you take a look?

Thanks,
Gary


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

[onap-discuss] [ONAP Helpdesk #55626] [linuxfoundation.org #55626] RE: Gerrit is down

[Gildas Lanilis via RT]

Wiki is down too.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gary Wu
Sent: Friday, May 04, 2018 11:13 AM
To: helpd...@onap.org; onap-discuss 
Subject: [onap-discuss] Gerrit is down

Hi Helpdesk,

gerrit.onap.org is down.  Can you take a look?

Thanks,
Gary



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

[onap-discuss] Gerrit is down

[Gary Wu]

Hi Helpdesk,

gerrit.onap.org is down.  Can you take a look?

Thanks,
Gary


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

[onap-discuss] A&AI service naming in OOM

[James MacNider]

Hi Harish,

I've got a question about the naming of the A&AI service in OOM that listens on 
port 8443.  Currently, this service is called simply 'aai', and is referred to 
as such by all clients.

$ kubectl get svc -n onap
NAME  TYPECLUSTER-IP  EXTERNAL-IP   PORT(S) 
AGE
aai   NodePort10.43.220.69
8080:30232/TCP,8443:30233/TCP   33s
aai-cassandra ClusterIP   None
9042/TCP,9160/TCP   34s
aai-elasticsearch ClusterIP   None9200/TCP
34s
aai-hbase ClusterIP   None
2181/TCP,8080/TCP,8085/TCP,9090/TCP,16000/TCP,16010/TCP,16201/TCP   34s
aai-modelloader   NodePort10.43.124.107   
8080:30210/TCP,8443:30229/TCP   34s
aai-resources ClusterIP   None
8447/TCP,5005/TCP   34s
aai-search-data   ClusterIP   None9509/TCP
34s
aai-sparky-be ClusterIP   None9517/TCP
33s
aai-traversal ClusterIP   None
8446/TCP,5005/TCP   33s

I noticed though that "aai-aai" is configured as the service name in 
oom/kubernetes/aai/values.yaml, and also in the values.yaml for aai-sparky-be:

$ grep -R aai-aai *
aai/values.yaml:serviceName: aai-aai
aai/charts/aai-sparky-be/values.yaml:serviceName: aai-aai


Is the "aai-aai" naming a relic that should be removed?

Thanks,

James MacNider
Software Architect

Open Network Division
Amdocs Technology
(office) (613)-595-5213

[amdocs-a]
Amdocs is a Platinuim Member of ONAP

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] [app-c] Ansible Server details in appc.properties file

[Anumaneni, Venkataramana (Nokia - US/Irving)]

Hello APPC team,

I am trying to update Ansible Server details in APPC properties file. But, we 
couldn't find exact parameter to be updated. Could you please provide sample 
appc.properties file which has Ansible Server details?

ariable Name

Description

Type

Comments

User

Username to logon to Ansible Server

Mandatory

Should be provided by APPC.

Password

Password to logon to Ansible Server

Mandatory

Should be provided by APPC.

AgentUrl

The complete URL of the Ansible Server to post the request for execution and 
retrieve results (if in synchronous mode)




Regards
Venkat


From: CHO, TAKAMUNE [mailto:tc0...@att.com]
Sent: Wednesday, April 04, 2018 3:56 PM
To: Akula, Ramanjaneyul Reddy (Nokia - US/Irving) 
; onap-discuss@lists.onap.org
Cc: Anumaneni, Venkataramana (Nokia - US/Irving) 
Subject: RE: [onap-discuss] [app-c] appc client library location

HI Ramu,

Thanks for interested on APPC.

It sounds like your local_setting.xml for mvn build has an issue, can you 
attach your local_setting to me, I can take a look.

Thanks

Taka

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Akula, Ramanjaneyul 
Reddy (Nokia - US/Irving)
Sent: Wednesday, April 04, 2018 3:27 PM
To: onap-discuss@lists.onap.org
Cc: ANUMANENI, VENKATA RAMANA 
mailto:venkataraman...@nokia.com>>
Subject: [onap-discuss] [app-c] appc client library location

Hi APPC Team,
We are planning to do some VNF configuration using APP-C. For the same, learned 
that we can use the APP-C client libraries (org.onap.appc.client:client-kit, 
org.onap.appc.client:client-lib) to send the LCM request to DMaaP topic 
(http://onap.readthedocs.io/en/latest/submodules/appc.git/docs/APPC%20Client%20Library%20Guide/APPC%20Client%20Library%20Guide.html#appc-client-library

However, we failed to located the needed jars.
Then tried to compile the code using the instructions @ 
"https://wiki.onap.org/display/DW/Building+Entire+ONAP"

While comping the APP-C code, getting below error:

[FATAL] Non-resolvable parent POM for org.onap.appc:appc:1.3.0-SNAPSHOT: 
Failure to find org.onap.ccsdk.parent:odlparent-carbon-sr1:pom:0.1.0 in 
https://repo.maven.apache.org/maven2
 was cached in the local repository, resolution will not be reattempted until 
the update interval of central has elapsed or updates are forced and 
'parent.relativePath' points at wrong local POM @ line 25, column 13
@

Can someone help me on how to get around this problem.


Thanks & best regards,
Ramu




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

[onap-discuss] Feedback on Casablanca priorities

[Alla Goldner]

Hi all,

We received a lot of feedback on Casablanca suggested priorities and missing 
requirements from SP forming End User Advisory Group.
I distributed the received feedback earlier and it is reflected on wiki.

The question is how we make sure this feedback is reflected, for balance 
between platform quality and enrichment, for the specific demanded use cases 
and for the functional/architecture gaps we are requested to fulfill. What 
would be the appropriate process to reflect it in our Casablanca plans?

Your feedback is appreciated!

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3E3DA.88963F40]

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] more feedback on Casablanca priorities received from Turk Telecom

[Alla Goldner]

https://wiki.onap.org/display/DW/Casablanca+goals

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3E3D9.F6004EA0]

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] OOM Beijing HW requirements

[Michal Ptacek]

 
Hi all,
 
I am trying to deploy latest ONAP (Beijing) using OOM (master branch) and I found some challenges using suggested HW resources for all-in-one (rancher server + k8s host on single node) deployment of ONAP:
 
HW resources:
   24 VCPU
128G RAM
500G disc space
rhel7.4 os
rancher 1.6.14
kubernetes 1.8.10
helm 2.8.2
kubectl 1.8.12
docker 17.03-ce
 
Problem:
some random pods are unable to spawn and are on "Pending" state with error "No nodes are available that match all of the
predicates: Insufficient pods (1).“
 
Analyzis:
it seems that mine server can allocate max. 110 pods, which I found from "kubectl describe nodes" output
...
Allocatable:
cpu: 24
memory:  102861656Ki
pods:    110
...
full ONAP deployment with all components enabled might be 120+ pods but I did not get even that 110 running,
maybe some race-condition for latest pods. If I disable 5+ components in onap/values.yaml, it will fit into that server but then it seems that "Minimum Hardware Configuration" described in
http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_cloud_setup_guide.html
is wrong (120GB RAM, 160G disc, 16vCPU)
 
or is there any hint how to increase that maximum number of allocatable pods ?
 
thanks,
Michal
 
 
 
 
 
 
 
  

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

[onap-discuss] OOM Beijing HW requirements

[Michal Ptacek]

Hi all,
 
I am trying to deploy latest ONAP (Beijing) using OOM (master branch) and I found some challenges using suggested HW resources for all-in-one (rancher server + k8s host on single node) deployment of ONAP:
 
HW resources:
   24 VCPU
128G RAM
500G disc space
rhel7.4 os
rancher 1.6.14
kubernetes 1.8.10
helm 2.8.2
kubectl 1.8.12
docker 17.03-ce
 
Problem:
some random pods are unable to spawn and are on "Pending" state with error "No nodes are available that match all of the
predicates: Insufficient pods (1).“
 
Analyzis:
it seems that mine server can allocate max. 110 pods, which I found from "kubectl describe nodes" output
...
Allocatable:
cpu: 24
memory:  102861656Ki
pods:    110
...
full ONAP deployment with all components enabled might be 120+ pods but I did not get even that 110 running,
maybe some race-condition for latest pods. If I disable 5+ components in onap/values.yaml, it will fit into that server but then it seems that "Minimum Hardware Configuration" described in
http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_cloud_setup_guide.html
is wrong (120GB RAM, 160G disc, 16vCPU)
 
or is there any hint how to increase that maximum number of allocatable pods ?
 
thanks,
Michal





 
  

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

[onap-discuss] DCAE deployment in R2 (oom or heat)

[Michal Ptacek]

Hi,
 
will it be possible to fully deploy DCAE using OOM in R2 ?
 
It seems that trend is to move to containers from VM's, also DCAE is going into this direction.
what I heard here https://wiki.onap.org/display/DW/Meetings?preview=/13598723/31982711/dcae-weekly-20180503.mp4
is that currently DCAE can be spawned on single bootstrap VM (8G-16G of RAM) and all components are running as docker containers, also it
should be possible to deploy it fully using OOM. 
I tried today to deploy latest ONAP in OOM (multinode, single node is not possible anymore with 110 pods per k8s host limitation) but I see just following dcae pods 
 
onap  beijing-dcae-cloudify-manager-fb9f5d6bd-bss2n  1/1   Running 0  4honap  beijing-dcae-db-0  1/1   Running 0  4honap  beijing-dcae-db-1  1/1   Running 0  2honap  beijing-dcae-healthcheck-78999885d5-5hts8  1/1   Running 0  4honap  beijing-dcae-redis-0   1/1   Running 0  4honap  beijing-dcae-redis-1   1/1   Running 0  3honap  beijing-dcae-redis-2   1/1   Running 0  2honap  beijing-dcae-redis-3   1/1   Running 0  2honap  beijing-dcae-redis-4   1/1   Running 0  2honap  beijing-dcae-redis-5   1/1   Running 0  1h 
 
where is the rest ?
please advise 
 
have a nice weekend
thanks,
Michal

 
  

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

Re: [onap-discuss] Visa Letters for China

[Kenny Paul]

Visa letters are being distributed this morning to those that have requested 
them.

 

Thanks!

-kenny

 

From: Kenny Paul 
Date: Monday, April 30, 2018 at 11:38 AM
To: "onap-discuss@lists.onap.org" 
Subject: Visa Letters for China

 

All, 

 

As a many of you are aware we have been impacted twice in as many weeks 
regarding visa letter generation for the Casablanca Developer Event.

We are intimately familiar with the issues and the criticality of the timing.  
It is actively being worked by the LF and I will send out an announcement once 
we have clear line of sight.

 

Best Regards, 
-kenny

Kenny Paul, Technical Program Manager, The Linux Foundation
kp...@linuxfoundation.org, 510.766.5945
San Francisco Bay Area, Pacific Time Zone

 

 

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

[onap-discuss] more feedback on Casablanca priorities received from Swisscom

[Alla Goldner]

https://wiki.onap.org/display/DW/Casablanca+goals

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3E3AF.B12DD830]

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] [Onap-usecasesub] Usecase subcommittee meeting of 30/4/2018 - the summary

[Vladimir Yanover (vyanover)]

Thanks, Tracy
Is there any (application level) reason why some RAN parameters cannot be 
configured, say, via NETCONF/YANG?
Is it because of the nature of these parameters?
Thanks
Vladimir

From: VAN BRAKLE, TRACY L 
Sent: Thursday, May 3, 2018 4:26 PM
To: Andrej Záň ; Vladimir Yanover (vyanover) 
; BEGWANI, VIMAL ; Stephen Terrill 
; Alla Goldner ; 
onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: RE: [Onap-usecasesub] [onap-discuss] Usecase subcommittee meeting of 
30/4/2018 - the summary

Andrej,

I suppose there are a variety of ways this could be implemented, as all three 
derive from CC-SDK.

SDN-R = CC-SDK + Mobility Wireless "artifacts"

Tracy

From: Andrej Záň mailto:andrej@pantheon.tech>>
Sent: Thursday, May 03, 2018 9:21 AM
To: VAN BRAKLE, TRACY L mailto:tv8...@att.com>>; Vladimir 
Yanover (vyanover) mailto:vyano...@cisco.com>>; BEGWANI, 
VIMAL mailto:vb1...@att.com>>; Stephen Terrill 
mailto:stephen.terr...@ericsson.com>>; Alla 
Goldner mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; 
onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: Re: [Onap-usecasesub] [onap-discuss] Usecase subcommittee meeting of 
30/4/2018 - the summary


Hello there,



I have one question (possibly stupid one, sorry for that).

You wrote that SDN-R will be SDN-C + APP-C functionality but for Mobility 
Wireless. Does that mean, that these functions can't be provided by some 
combination/cooperation of SDN-C and APP-C themselves?


Regards

Andrej Záň


Od: VAN BRAKLE, TRACY L mailto:tv8...@att.com>>
Odoslané: štvrtok, 3. mája 2018 15:07
Komu: Vladimir Yanover (vyanover); BEGWANI, VIMAL; Stephen Terrill; Alla 
Goldner; onap-usecase...@lists.onap.org
Kópia: onap-...@lists.onap.org; 
onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Predmet: Re: [Onap-usecasesub] [onap-discuss] Usecase subcommittee meeting of 
30/4/2018 - the summary


Vladimir,



As of now, the expectation is that all categories of parameters would be 
supported by the ONAP controller derived from CC-SDK for Mobility Wireless.



We have dubbed this controller "SDN-R," as you know, because this particular 
label has meaning (traction, actually) within both ONAP and ONF.



SDN-R = SDN-C + APP-C for Mobility Wireless, in other words.



What we do not yet know is what will be configured via Netconf/YANG versus what 
will be configured via Ansible, but I believe the community will have this 
question answered fairly early within the Casblanca release timeframe.



Tracy



From: Vladimir Yanover (vyanover) 
mailto:vyano...@cisco.com>>
Sent: Thursday, May 03, 2018 4:09 AM
To: VAN BRAKLE, TRACY L mailto:tv8...@att.com>>; BEGWANI, VIMAL 
mailto:vb1...@att.com>>; Stephen Terrill 
mailto:stephen.terr...@ericsson.com>>; Alla 
Goldner mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; 
onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: RE: [Onap-usecasesub] [onap-discuss] Usecase subcommittee meeting of 
30/4/2018 - the summary



Tracy, Steve and Vimal

I have to admit that I am confused as well and need your help.

Which categories of parameters will be supported by the SDN-R?

Which categories of "the parameters needed for DU & CUs" cannot be supported by 
the SDN-R (why?) and will be supported by the APP-C?

Thanks

Vladimir





From: 
onap-usecasesub-boun...@lists.onap.org
 
mailto:onap-usecasesub-boun...@lists.onap.org>>
 On Behalf Of VAN BRAKLE, TRACY L
Sent: Thursday, May 3, 2018 12:04 AM
To: BEGWANI, VIMAL mailto:vb1...@att.com>>; Stephen Terrill 
mailto:stephen.terr...@ericsson.com>>; Alla 
Goldner mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; 
onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: Re: [Onap-usecasesub] [onap-discuss] Usecase subcommittee meeting of 
30/4/2018 - the summary



Whatever we elect to call it, "SDN-R" in Casablanca is evolving to include all 
(or most) logic + features/functionality derived from CC-SDK, whether 
considered "SDN-C" or "APP-C."  This will include Ansible and Chef interfaces 
as well as the additional parameters that may be defined/documented within ONAP 
or within a related open source project.



Refer to the "ONAP OAM Controller" slid

[onap-discuss] Usecase subcommittee meeting on May 7th - the agenda

[Alla Goldner]

Hi all,

Here is agenda for Usecase subcommittee meeting next week:


1.   As agreed with Helen, we will dedicate 30 minutes to PNF support and 
scaling out (Beijing) use cases status of integration work - 
Scott/Zhao/Ben/Vimal



2.   Short reviews of Casablanca use cases proposals status - as we have to 
bring them for approval by the TSC next Thursday - all Casablanca use cases 
task forces leads

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3E3A4.2C3D4170]

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] OOM Beijing HW requirements

[Michal Ptacek]

Hi all,
 
I am trying to deploy latest ONAP (Beijing) using OOM (master branch) and I found some challenges using suggested HW resources for all-in-one (rancher server + k8s host on single node) deployment of ONAP:
 
HW resources:
   24 VCPU
128G RAM
500G disc space
rhel7.4 os
rancher 1.6.14
kubernetes 1.8.10
helm 2.8.2
kubectl 1.8.12
docker 17.03-ce
 
Problem:
some random pods are unable to spawn and are on "Pending" state with error "No nodes are available that match all of the
predicates: Insufficient pods (1).“
 
Analyzis:
it seems that mine server can allocate max. 110 pods, which I found from "kubectl describe nodes" output
...
Allocatable:
cpu: 24
memory:  102861656Ki
pods:    110
...
full ONAP deployment with all components enabled might be 120+ pods but I did not get even that 110 running,
maybe some race-condition for latest pods. If I disable 5+ components in onap/values.yaml, it will fit into that server but then it seems that "Minimum Hardware Configuration" described in
http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_cloud_setup_guide.html
is wrong (120GB RAM, 160G disc, 16vCPU)
 
or is there any hint how to increase that maximum number of allocatable pods ?
 
thanks,
Michal
 
 
 
 
 
 
 
 
  

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