Re: [onap-discuss] [onap-tsc] e2e use cases for approval by the TSC

2018-05-13 Thread Vladimir Yanover (vyanover) 
Thanks, Alla,
Small correction: my comment was about slicing optimization, not slicing 
support in general. We may need to work more on slicing support, but finally it 
will be done.
Vladimir

From: Alla Goldner 
Sent: Saturday, May 12, 2018 9:08 AM
To: Vladimir Yanover (vyanover) ; 
onap-usecase...@lists.onap.org; onap-tsc ; 
onap-discuss@lists.onap.org
Subject: RE: [onap-tsc] e2e use cases for approval by the TSC

Thanks, Vladimir,

5G task force: the following requests were received:


1.   SON support

2.   Network slicing support

3.   Controllers architecture

I attach them to this email.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EAB4.83F83110]

From: Vladimir Yanover (vyanover) [mailto:vyano...@cisco.com]
Sent: Saturday, May 12, 2018 6:17 PM
To: Alla Goldner >; 
onap-usecase...@lists.onap.org; onap-tsc 
>; 
onap-discuss@lists.onap.org
Subject: RE: [onap-tsc] e2e use cases for approval by the TSC

Hi, Alla,

Thanks for sending this. To my deep regret, there is a problem. Cisco several 
times expressed opposition to having SON in this release. The reason is that 
the architecture for SON was never properly analyzed.
Therefore I request removal of the following items

1.   SON - problem formulation

2.   SON - problem solving

3.   Slice optimization problem formulation

4.   Slice optimization problem solving
For all four, the concern is about splitting of the SON procedure(s) into two 
independent pieces.
For #3 and #4, in addition to that, there is no consistent definition yet (in 
3GPP) of slice level performance measurements. With no performance 
measurements, what kind of optimization can be arranged?

Thanks
Vladimir


From: Alla Goldner >
Sent: Friday, May 11, 2018 11:34 AM
To: Vladimir Yanover (vyanover) 
>; 
onap-usecase...@lists.onap.org; onap-tsc 
>; 
onap-discuss@lists.onap.org
Subject: RE: [onap-tsc] e2e use cases for approval by the TSC

Hi Vladimir,

The implementation proposals for 5G use cases in Casablanca was also discussed 
during several Usecase subcommittee meetings and presentation is uploaded for 
yesterday's TSC meting 
https://wiki.onap.org/pages/editpage.action?pageId=28381537

I also attach it.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EAB4.83F83110]

From: Vladimir Yanover (vyanover) [mailto:vyano...@cisco.com]
Sent: Friday, May 11, 2018 11:24 AM
To: Alla Goldner >; 
onap-usecase...@lists.onap.org; onap-tsc 
>; 
onap-discuss@lists.onap.org
Subject: RE: [onap-tsc] e2e use cases for approval by the TSC

Alla,
Can you please clarify what exactly you received from 5G group?
Unless I am missing something, there was no 5G call to finally decide which use 
cases are going to the use case subcommittee. There were several proposals 
presented, most of them good, but even for those I have difficulty to 
understand which of them (and which versions) have been ever endorsed by the 5G 
group.
Thanks
Vladimir

From: onap-tsc-boun...@lists.onap.org 
> On 
Behalf Of Alla Goldner
Sent: Friday, May 11, 2018 7:58 AM
To: onap-usecase...@lists.onap.org; 
onap-tsc >; 
onap-discuss@lists.onap.org
Subject: [onap-tsc] e2e use cases for approval by the TSC

Hi all,

As we didn't have any time left for use case discussion and approval during 
yesterday's TSC meeting and likely will not have till the launch of Beijing due 
to urgent Beijing related discussions, the meeting decision was that we will 
host e2e use case approval discussions during Usecase subcommittee meetings on 
Monday, 4 pm CET.


1.   All use case authors - please make sure you distributed your 
presentations for approval. So far, we've received 5G group, Edge Automation 
and auto Scaling out

2.   Kenny, as agreed, please make sure all PTLs aware the discussion will 
take place during Use case subcommittee meeting

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EAB4.83F83110]

This message and the information contained herein is proprietary and

Re: [onap-discuss] [oom] [aai] Resources fails to start

2018-05-13 Thread Borislav Glozman 
Hi,

I invested today in researching this problem. It occurs on non-Rancher 
environments.
I realized that aai-cassandra chart, specially service is not well. There was a 
problem with label app, it didn’t match the statefulSet.
This caused a strange behavior on Rancher, where serviceName defined in the 
stateful set was routable. But on other k8s deployments it wasn’t.

Note the annotation that is needed for successful start of Cassandra:
service.alpha.kubernetes.io/tolerate-unready-endpoints: "true"
Also note that the publishNotReadyAddresses field that is supposed to replace 
this annotation is not working 
(https://github.com/kubernetes/kubernetes/issues/58662).
Had to update resources and traversal configuration.

Finally I managed to make it work in both Rancher and my kubeadm multimode 
environment (versions 1.7.16 and 1.10.1).

Some Cassandra instances sometimes need a couple of restarts before they manage 
to start successfully, but it resolves quickly.
If there is some Cassandra expert from aai team that would like to improve the 
Cassandra start process, you are most welcome.

The fix is in a pending review: https://gerrit.onap.org/r/47323

Runcher:
root@borislav-new-rancher:~/onap/master/aai/oom/kubernetes# kgpa -w
NAMESPACE NAMEREADY STATUS  
RESTARTS   AGE
kube-system   heapster-76b8cd7b5-l9sdn1/1   Running 
1  28d
kube-system   kube-dns-5d7b4487c9-j5ctf   3/3   Running 
15 28d
kube-system   kubernetes-dashboard-f9577fffd-9sqfc1/1   Running 
1  28d
kube-system   monitoring-grafana-997796fcf-krq9l  1/1   Running 
1  28d
kube-system   monitoring-influxdb-56fdcd96b-tvtm2 1/1   Running 
1  28d
kube-system   tiller-deploy-54bcc55dd5-sxcl2  1/1   Running 
4  28d
onap  aaa-aai-85684bcf79-ddrj81/1   Running 
0  5m
onap  aaa-aai-babel-7ff8f4d4-hlfqs2/2   Running 
0  5m
onap  aaa-aai-cassandra-0 1/1   Running 
2  5m
onap  aaa-aai-cassandra-1 1/1   Running 
0  3m
onap  aaa-aai-cassandra-2 1/1   Running 
0  3m
onap  aaa-aai-champ-6857876bff-dl72c  0/1   Running 
0  5m
onap  aaa-aai-data-router-5b48bc6f78-n4wgb1/1   Running 
0  5m
onap  aaa-aai-elasticsearch-ccd96645c-jrfqn   1/1   Running 
0  5m
onap  aaa-aai-gizmo-6966c665c5-9wjwf  2/2   Running 
0  5m
onap  aaa-aai-hbase-57f86cc86c-8q995  1/1   Running 
0  5m
onap  aaa-aai-modelloader-7b5fc6f474-462t72/2   Running 
0  5m
onap  aaa-aai-resources-7f9ddc68dc-shkcv  2/2   Running 
0  5m
onap  aaa-aai-search-data-cd976775f-fnstt 2/2   Running 
0  5m
onap  aaa-aai-sparky-be-6d8978bdbb-8dzzq  2/2   Running 
0  5m
onap  aaa-aai-traversal-6c58f8d698-6pchw  2/2   Running 
0  5m
onap  aaa-aai-traversal-update-query-data-bpfcw   0/1   
Completed   0  5m
onap  aaa-dbc-pg-01/1   Running 
0  5m
onap  aaa-dbc-pg-11/1   Running 
0  3m
onap  aaa-dmaap-bus-controller-595dfd5779-f68rc   1/1   Running 
0  5m
onap  aaa-message-router-5c694bbdcc-vxnzd 1/1   Running 
0  5m
onap  aaa-message-router-kafka-d6689b986-ncrtq1/1   Running 
0  5m
onap  aaa-message-router-zookeeper-85f48f46b6-n2z9p   1/1   Running 
0  5m

Kubeadm:
onap  aaa-aai-7bf94cd486-982zj  
  1/1   Running 0  20m   10.244.6.18
kubernetes-node6-borislavto-13099-05-13-18.novalocal
onap  aaa-aai-babel-6485c7944b-55ghh
  2/2   Running 0  20m   10.244.6.17
kubernetes-node6-borislavto-13099-05-13-18.novalocal
onap  aaa-aai-cassandra-0   
  1/1   Running 0  20m   10.244.6.19
kubernetes-node6-borislavto-13099-05-13-18.novalocal
onap  aaa-aai-cassandra-1   
  1/1   Running 0  19m   10.244.3.15
kubernetes-node2-borislavto-13099-05-13-18.novalocal
onap

[onap-discuss] Requirements extracted from SP lists of priorities for Casablanca

2018-05-13 Thread Alla Goldner 
Hi all,

I extracted common requirements received from a different Service Providers for 
Casablanca Release so far and put them under: 
https://wiki.onap.org/display/DW/Requirements+extracted+from+SP+lists+of+priorities+for+Casablanca

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EA99.9885AE70]

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