date:20171212

[onap-discuss] [openstack-install] Reg. Amsterdam release bring-up

2017-12-12 Thread ESWAR RAO

Hi All,

I am following
http://onap.readthedocs.io/en/latest/guides/onap-developer/settingup/fullonap.html
,

to bring-up ONAP on openstack infra.


My plan is to install openstack through openstack-ansible.

Please let me know if there is any recommended way of openstack
installation instead of ansible way  or is it good to go model ??


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

[onap-discuss] Hi Michael, could you please upload the vcr of SDC Modeling Session on Dec 12? Thanks

2017-12-12 Thread feng.yuanxing

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

[onap-discuss] [sdnc] SDNC Weekly call cancelled this week due to f2f

2017-12-12 Thread TIMONEY, DAN

SDNC team

I’m canceling our normal SDNC meeting this week since many of us will be 
attending the ONAP developer face to face event.

For those of you attending that event, I reserved a breakout room at 11:20 AM 
tomorrow California time for us to get together to discuss Beijing release 
contents. I’ll send more on that later this evening.

Dan

Sent from MyOwn, an AT BYOD solution.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [ONAP Helpdesk #49130] Branch creation permissions

2017-12-12 Thread Jessica Wagantall via RT

Rejecting... 

Please re-open this request if it becomes needed again.

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

[onap-discuss] F2F Santa Clara Presentation

2017-12-12 Thread Gildas Lanilis

Hi,

As a lot people have asked here is the link toward the presentation I made at 
Santa Clara F2F.
https://wiki.onap.org/display/DW/ONAP+Dec+2017+F2F+in+Santa+Clara


Thanks,
Gildas

[HuaweiLogowithName]
Gildas Lanilis
ONAP Release Manager
Santa Clara CA, USA
gildas.lani...@huawei.com
Mobile: 1 415 238 6287

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

Re: [onap-discuss] [oom] Issue in ONAP Amsterdam release installation

2017-12-12 Thread Potter, Nathaniel

Hi all,

I've seen some of these errors somewhat sporadically, but sometimes when I tear 
down and redeploy making no changes they'll come up correctly. The failure that 
I see in the pod is usually a sync error, like the following error in the 
aai-service pod that leads to the readiness container erroring out and the pod 
getting stuck in an init state:

Events:
  Type Reason Age From  
  Message
   --   
  ---
  Normal   Scheduled  29m default-scheduler 
  Successfully assigned aai-service-749944520-5dks6 to otconap3.sc.intel.com
  Normal   SuccessfulMountVolume  29m kubelet, 
otconap3.sc.intel.com  MountVolume.SetUp succeeded for volume "localtime"
  Normal   SuccessfulMountVolume  29m kubelet, 
otconap3.sc.intel.com  MountVolume.SetUp succeeded for volume "haproxy-cfg"
  Normal   SuccessfulMountVolume  29m kubelet, 
otconap3.sc.intel.com  MountVolume.SetUp succeeded for volume "aai-service-log"
  Normal   SuccessfulMountVolume  29m kubelet, 
otconap3.sc.intel.com  MountVolume.SetUp succeeded for volume 
"default-token-60hch"
  Normal   Pulling9m (x2 over 27m)kubelet, 
otconap3.sc.intel.com  pulling image "oomk8s/readiness-check:1.0.0"
  Normal   Pulled 9m (x2 over 20m)kubelet, 
otconap3.sc.intel.com  Successfully pulled image "oomk8s/readiness-check:1.0.0"
  Normal   Created9m (x2 over 20m)kubelet, 
otconap3.sc.intel.com  Created container
  Normal   Started9m (x2 over 20m)kubelet, 
otconap3.sc.intel.com  Started container
  Warning  FailedSync 9m  kubelet, 
otconap3.sc.intel.com  Error syncing pod


In this same deployment my sdc-fe pod is getting the same sync error, is that 
the same warning you're seeing?

Here's the final output of 'kubectl get pods --all-namespaces -a -o wide' in my 
setup.
https://hastebin.com/mototaqihe.nginx

Thanks,
Nate Potter

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Borislav Glozman
Sent: Tuesday, December 12, 2017 3:13 AM
To: Pavithra R13 ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [oom] Issue in ONAP Amsterdam release installation

Please kindly send logs.
The DNS warning is normal when using rancher 1.6.10, please ignore it. There 
may be some other error.
Have you deployed config? Please provide output of 'kubectl get pods 
--all-namespaces -a -o wide'

Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726

From: Pavithra R13 [mailto:pavithra_...@infosys.com]
Sent: Tuesday, December 12, 2017 4:08 AM
To: onap-discuss@lists.onap.org; Borislav 
Glozman >
Subject: RE: [oom] [onap-discuss] Issue in ONAP Amsterdam release installation

Hi

We downloaded the latest oom and were able to proceed but now the fe and be of 
SDC , vnc portal and dmaap, global Kafka of message router are not coming up 
due to error "search line limits were exceeded. Some dns names were omitted". 
We have Internet access without any firewall and we have configured google dns 
in resolv.conf . So kindly help us in resolving this issue .

Regards
Pavithra




From: Borislav Glozman 
>
Date: 11 December 2017 at 5:54:01 PM IST
To: onap-discuss@lists.onap.org 
>, Pavithra R13 
>
Subject: RE: [onap-discuss] Issue in ONAP Amsterdam release installation

Hi,

Please add [oom] in subject.
These workings you mentioned are not important and can be ignored. They are 
related to some Rancher bug that is supposed to be fixed.

Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Pavithra R13
Sent: Monday, December 11, 2017 1:38 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Issue in ONAP Amsterdam release installation

Hi All

While trying to install ONAP Amsterdam release we are facing issue in bringing 
up message router(dmaap, global-kafka), vnc portal and sdc(be, fe) containers. 
The error is "searchline limits were exceeded, some dns names have been 
omitted." We have prepulled 1.1.10 branch and using v1.6.10 of rancher and 2.3 
version of helm. We have set nameserver as 8.8.8.8 in /etc/resolv.conf. Please 
find attached screen shot of error and kindly help us in resolving the issue.

Thanks & Regards,
Pavithra

Re: [onap-discuss] Queue full error while trying to submit VES event

2017-12-12 Thread VENKATESH KUMAR, VIJAY

HI Kedar,
The queue full is resultant of dmaap publish failure for prolonged time. Once 
the DMAAP errors are resolved, collector will publish the queued events 
automatically (provided the DMAAP configuration was set correct during startup).

Also based on the URL posted -   should be replaced with actual 
DMAAP Host IP (if you are using standalone setup, this IP should be provided 
during VES Container startup). Some of the details are documented here - 
https://wiki.onap.org/pages/viewpage.action?pageId=16002279#DCAEmSDeployment(Standaloneinstantiation)-VESCollector

Thanks,
Vijay

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kedar Ambekar
Sent: Monday, December 11, 2017 11:55 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Queue full error while trying to submit VES event

Hi Team,

On DCAE collector, if I try to submit a VES event, I get "queue full" error.  
What could be wrong ?

curl -i  -X POST -d "@dataFile.json" --header "Content-Type:application/json" 
-k http://localhost:8080/eventListener/v5

HTTP/1.1 503 Service Unavailable
Server: Apache-Coyote/1.1
X-Rathravane: ~ software is craft ~
Content-Type: application/json;charset=ISO-8859-1
Content-Length: 74
Date: Fri, 08 Dec 2017 14:09:59 GMT
Connection: close
{"requestError":{"GeneralException":{"Status":503,"Error":"Queue full"}}}


http://:3904/events/unauthenticated.SEC_MEASUREMENT_OUTPUT
 also doesn't work.

I see some errors in dmaap and kafka container logs on message router VM. If I 
restart them, will subscriptions remain intact ?

Disclaimer:  This message and the information contained herein is proprietary 
and confidential and subject to the Tech Mahindra policy statement, you may 
review the policy at 
http://www.techmahindra.com/Disclaimer.html
 externally 
http://tim.techmahindra.com/tim/disclaimer.html
 internally within TechMahindra.

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

Re: [onap-discuss] [rancher][onap discuss] Amsterdam release installation

2017-12-12 Thread Michael O'Brien

Hi, Pavithra
  Check the aws video at the top of the page - and the CD server - expected 
time is about 25 min to come up and 40 min to fully healthcheck, running robot 
init.
  There is a mail previously I sent with 10 causes
  Verify that your config container is OK - you sourced setenv to pull in 
docker variables - usually you would have half the containers in init.
  Verify that all dependent containers are up - for example portal will not 
start until sdc is up - sdc has its own dependencies in the yaml.
  As a first test bring up all 87 containers - to avoid dependency issues
  Check the logs on containers past the init state
  HD size will block you  - make sure you have 75G+ for /dockerdata-nfs
  Make sure you have pulled the latest from release-1.1.0 - remember if you 
previously ran then a copy of your onap-parameters.yaml will cause a git status 
(modified)
  Post a kubectl get pods -all-namespaces -a
  Then we can see the structure of your failures and can see if it is a docker 
pull issue (a lot of failures in init) - or a dependency issues - missing pods
  Thank you
   /michael

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Pavithra R13
Sent: Tuesday, December 12, 2017 06:46
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [rancher][onap discuss] Amsterdam release installation

Hi All,

The Rancher installation, Host registration in Kubernetes and the ONAP 
containers(They are in container creating state , taking overnight to come to 
running state) are taking a lot of time to come up , almost a whole day in 
Amsterdam release even after prepulling docker images . Could you please let me 
know if this is the expected behavior or if anybody else is facing the same 
state.

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 

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

Re: [onap-discuss] [rancher][onap discuss] Amsterdam release installation

2017-12-12 Thread Alexis de Talhouët

Hi,

This is very dependent on the resources you provided your K8S hosts. Give it 
enough memory and CPU, around 64GO mem, 4 to 8 vCPU (you’ll have faster results 
with 8), and also, I found out yesterday, give it like 16GO of swap, as a lot 
of those apps are idle, it’s ok to swap. With such resources, (4 vCPUs), it’s 
taking around 50 mn from scratch.
Of course, connectivity is important, but you said you pre-pull the images, so 
that should help.

HTH,
Alexis

> On Dec 12, 2017, at 6:46 AM, Pavithra R13  wrote:
> 
> Hi All,
>  
> The Rancher installation, Host registration in Kubernetes and the ONAP 
> containers(They are in container creating state , taking overnight to come to 
> running state) are taking a lot of time to come up , almost a whole day in 
> Amsterdam release even after prepulling docker images . Could you please let 
> me know if this is the expected behavior or if anybody else is facing the 
> same state.
>  
> Thanks & Regards,
> Pavithra R
>  
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org 
> https://lists.onap.org/mailman/listinfo/onap-discuss 
> 
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [rancher][onap discuss] Amsterdam release installation

2017-12-12 Thread Pavithra R13

Hi All,

The Rancher installation, Host registration in Kubernetes and the ONAP 
containers(They are in container creating state , taking overnight to come to 
running state) are taking a lot of time to come up , almost a whole day in 
Amsterdam release even after prepulling docker images . Could you please let me 
know if this is the expected behavior or if anybody else is facing the same 
state.

Thanks & Regards,
Pavithra R

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

Re: [onap-discuss] [oom] Issue in ONAP Amsterdam release installation

2017-12-12 Thread Borislav Glozman

Please kindly send logs.
The DNS warning is normal when using rancher 1.6.10, please ignore it. There 
may be some other error.
Have you deployed config? Please provide output of 'kubectl get pods 
--all-namespaces -a -o wide'

Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726

From: Pavithra R13 [mailto:pavithra_...@infosys.com]
Sent: Tuesday, December 12, 2017 4:08 AM
To: onap-discuss@lists.onap.org; Borislav Glozman 
Subject: RE: [oom] [onap-discuss] Issue in ONAP Amsterdam release installation

Hi

We downloaded the latest oom and were able to proceed but now the fe and be of 
SDC , vnc portal and dmaap, global Kafka of message router are not coming up 
due to error "search line limits were exceeded. Some dns names were omitted". 
We have Internet access without any firewall and we have configured google dns 
in resolv.conf . So kindly help us in resolving this issue .

Regards
Pavithra




From: Borislav Glozman 
>
Date: 11 December 2017 at 5:54:01 PM IST
To: onap-discuss@lists.onap.org 
>, Pavithra R13 
>
Subject: RE: [onap-discuss] Issue in ONAP Amsterdam release installation

Hi,

Please add [oom] in subject.
These workings you mentioned are not important and can be ignored. They are 
related to some Rancher bug that is supposed to be fixed.

Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Pavithra R13
Sent: Monday, December 11, 2017 1:38 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Issue in ONAP Amsterdam release installation

Hi All

While trying to install ONAP Amsterdam release we are facing issue in bringing 
up message router(dmaap, global-kafka), vnc portal and sdc(be, fe) containers. 
The error is "searchline limits were exceeded, some dns names have been 
omitted." We have prepulled 1.1.10 branch and using v1.6.10 of rancher and 2.3 
version of helm. We have set nameserver as 8.8.8.8 in /etc/resolv.conf. Please 
find attached screen shot of error and kindly help us in resolving the issue.

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
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] Issue in ONAP Amsterdam release installation

2017-12-12 Thread Pavithra R13

Hi Glozman,

We are currently installing 1.1.0 branch of oom only. Even then we are facing 
issue in sdc(be,fe), vnc portal, message router (dmaap, global kafka) 
containers. Those containers are not coming to running state.

Regards,
Pavithra R

From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com]
Sent: Tuesday, December 12, 2017 11:45 AM
To: ruijing@intel.com; onap-discuss@lists.onap.org; Pavithra R13 
; Michael O'Brien 
Subject: RE: [onap-discuss] Issue in ONAP Amsterdam release installation

Please try installing branch release 1.1.0 of oom, it should be stable.

Thanks,
Borislav Glozman
O. +972-9-7669188
M. +972-52-2835726

-Original Message-
From: Pavithra R13 [pavithra_...@infosys.com]
Received: Tuesday, 12 Dec 2017, 4:50
To: onap-discuss@lists.onap.org 
[onap-discuss@lists.onap.org]; Borislav Glozman [borislav.gloz...@amdocs.com]; 
Michael O'Brien [frank.obr...@amdocs.com]; Guo, Ruijing [ruijing@intel.com]
Subject: RE: [onap-discuss] Issue in ONAP Amsterdam release installation
Thanks Ruijung. How to fix this issue or if it's from ONAP side ,when this 
issue will be fixed so that we can start deployment again.

Regards,
Pavithra




From: Guo, Ruijing >
Date: 12 December 2017 at 7:58:08 AM IST
To: Borislav Glozman 
>, Michael 
O'Brien >, Pavithra R13 
>, 
onap-discuss@lists.onap.org 
>
Subject: RE: [onap-discuss] Issue in ONAP Amsterdam release installation

Hi,

I can deploy ONAP using kubeadm + k8s 1.7.11 + helm 2.7.2 + oom with 2 or 3 
pods not working before.

Recently, ONAP has some regression:

1. 73 Running:
vagrant@onap:~$ kubectl get pods --all-namespaces  | grep onap | grep Run | wc
 73 4388176

2. 6 not Running (I think aai & sdc are regression)
vagrant@onap:~$ kubectl get pods --all-namespaces  | grep onap | grep -v Run
onap-aai  aai-service-749944520-rq3hj   0/1   
Init:0/11231d
onap-aai  aai-traversal-2843093465-twsz70/2   
Init:0/11241d
onap-kube2msb kube2msb-registrator-4293827076-pl5kh 0/1   
CrashLoopBackOff2691d
onap-portal   vnc-portal-3680188324-55m5r   0/1   
Init:2/51221d
onap-sdc  sdc-be-754421819-x9z030/2   
ImageInspectError   0  1d
onap-sdc  sdc-fe-902103934-s92q10/2   
Init:0/11241d

Thanks,
-Ruijing

-Original Message-
From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Pavithra R13
Sent: Tuesday, December 12, 2017 10:11 AM
To: Michael O'Brien >; 
Borislav Glozman 
>; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Issue in ONAP Amsterdam release installation

Hi Brien

We downloaded the latest oom and were able to proceed but now the fe and be of 
SDC , vnc portal and dmaap, global Kafka of message router are not coming up 
due to error "search line limits were exceeded. Some dns names were omitted". 
We have Internet access without any firewall and we have configured google dns 
in resolv.conf . So kindly help us in resolving this issue .

Regards
Pavithra



From: Michael O'Brien >
Date: 11 December 2017 at 7:39:58 PM IST
To: Pavithra R13 >, 
Borislav Glozman 
>, 
onap-discuss@lists.onap.org 
>
Subject: RE: [onap-discuss] Issue in ONAP Amsterdam release installation

Pavithra,
   I have it backwards - jetlag.
   You are OK for helm 2.3 - it is just as Borislav said - your repo is very 
old - that change occurred around the 14th of Nov and was fixed about 10 days 
later (oom-420/441 a couple other ones).
Thank you
   /michael


From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Michael O'Brien
Sent: Monday, December 11, 2017 08:56
To: Borislav Glozman 
>; Pavithra R13

[onap-discuss] Installation ONAP on K8S, stuck at helm chart installation for config pod creation

2017-12-12 Thread Li, Jeffrey (NSB - CN/Chengdu)

Hi,

I am installation ONAP on Kubernete on EE Cloud (openstack based), following 
the instructions on wiki: 
https://wiki.onap.org/display/DW/ONAP+on+Kubernetes#ONAPonKubernetes-ONAPMinimumR1InstallationHelmApps

Everything is ok until creating the config pod.
root@onap3:~/oom/kubernetes/config# ./createConfig.sh -n onap
 Creating configuration for ONAP instance: onap
namespace "onap" created
E1212 06:24:00.690049   31344 portforward.go:175] lost connection to pod
Error: transport is closing
 Done 

I tried many times from scratch and problem remains the same.

root@onap3:~/oom/kubernetes/config# helm version
Client: {SemVer:"v2.3.0", 
GitCommit:"d83c245fc324117885ed83afc90ac74afed271b4", GitTreeState:"clean"}
Server: {SemVer:"v2.3.0", 
GitCommit:"d83c245fc324117885ed83afc90ac74afed271b4", GitTreeState:"clean"}


Any ideas on this helm error, I googling and no found the answer.


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

[onap-discuss] [openstack-install] Reg. Amsterdam release bring-up

[onap-discuss] Hi Michael, could you please upload the vcr of SDC Modeling Session on Dec 12? Thanks

[onap-discuss] [sdnc] SDNC Weekly call cancelled this week due to f2f

[onap-discuss] [ONAP Helpdesk #49130] Branch creation permissions

[onap-discuss] F2F Santa Clara Presentation

Re: [onap-discuss] [oom] Issue in ONAP Amsterdam release installation

Re: [onap-discuss] Queue full error while trying to submit VES event

Re: [onap-discuss] [rancher][onap discuss] Amsterdam release installation

Re: [onap-discuss] [rancher][onap discuss] Amsterdam release installation

[onap-discuss] [rancher][onap discuss] Amsterdam release installation

Re: [onap-discuss] [oom] Issue in ONAP Amsterdam release installation

Re: [onap-discuss] Issue in ONAP Amsterdam release installation

[onap-discuss] Installation ONAP on K8S, stuck at helm chart installation for config pod creation

13 matches

Site Navigation

Mail list logo

Footer information