Re: [onap-discuss] OOM Casablanca - Install #oom
Jobs are supposed to be in “Completed” state. This is normal. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: onap-discuss@lists.onap.org On Behalf Of jkzcristiano Sent: Saturday, December 1, 2018 5:36 PM To: Brian ; onap-discuss@lists.onap.org Subject: Re: [onap-discuss] OOM Casablanca - Install #oom Hi all, I tried to deploy some services at once but I have found several issues. All issues seem to be that job pods get stuck in Completed state. Concretely, SDC had a number ot them in Completed and one pod degenerates in Init:Error state. Moreover, as time goes on new pods are created with status Init:Error. Example of my first deploy output is attached. Since SDC was the service with more errors then I decided to remove my onap install and just deploy SDC from scratch. The same behavior occurs: ubuntu@rancher:~/oom/kubernetes$ kubectl get pods -n onap NAME READY STATUS RESTARTS AGE dev-sdc-sdc-be-config-backend-6zb6f 0/1 Completed0 31m dev-sdc-sdc-be-d4cfcf55f-l5t4k 2/2 Running 0 31m dev-sdc-sdc-cs-58896d98d5-fwcgt1/1 Running 0 31m dev-sdc-sdc-cs-config-cassandra-9qtcw0/1 Completed0 31m# Initially this pod were in 1/1 Running and then changed to 0/1 Completed dev-sdc-sdc-dcae-be-5c68f985d9-sc9lt 2/2 Running 0 31m dev-sdc-sdc-dcae-be-tools-px4ks 0/1 Completed 0 21m # This pod is replicated with time. Its replicas are in Init:Error (example line below) dev-sdc-sdc-dcae-be-tools-rkp9x 0/1 Init:Error 0 31m dev-sdc-sdc-dcae-dt-85b9bc48c6-z4pm9 2/2 Running 0 31m dev-sdc-sdc-dcae-fe-c7c478686-rkkqm 2/2 Running 0 31m dev-sdc-sdc-dcae-tosca-lab-58dcd79f96-brr4n 2/2 Running 0 31m dev-sdc-sdc-es-5d6dd455c9-6wqh6 1/1 Running 0 31m dev-sdc-sdc-es-config-elasticsearch-ccsvp 0/1 Completed0 31m dev-sdc-sdc-fe-6995fcb6b4-8llds 2/2 Running 0 31m dev-sdc-sdc-kb-787b68d69c-npb95 1/1 Running 0 31m dev-sdc-sdc-onboarding-be-68b778d8b8-l55k2 2/2 Running 0 31m dev-sdc-sdc-onboarding-be-cassandra-init-5krq8 0/1 Completed0 31m dev-sdc-sdc-wfd-be-6bbf67855c-x58lt 1/1 Running 0 31m dev-sdc-sdc-wfd-be-workflow-init-k2m7f 0/1 Completed0 31m dev-sdc-sdc-wfd-fe-7f86d844d4-zr9ks 2/2 Running 0 31m The behavior I exemplified above (new pods are created with Init:Error state) seems to happen in SDC for all pods that are in Completed state as time goes on (as you can observe in the atached file). An example of a describe is below (similar output in Completed pods): ubuntu@rancher:~/oom/kubernetes$ kubectl -n onap describe pod dev-sdc-sdc-cs-config-cassandra-9qtcw Name: dev-sdc-sdc-cs-config-cassandra-9qtcw Namespace: onap Node: compute1/10.0.0.31 Start Time: Sat, 01 Dec 2018 12:33:58 + Labels: app=sdc-cs-job controller-uid=5d402721-f565-11e8-8341-02a92dbcc0b8 job-name=dev-sdc-sdc-cs-config-cassandra release=dev-sdc Annotations: Status: Succeeded IP: 10.42.161.88 Controlled By: Job/dev-sdc-sdc-cs-config-cassandra Init Containers: sdc-cs-init-readiness: Container ID: docker://49350127f3e91f70f8e4371458a1b635accbf50e534d32081a61c18939fc404c Image: oomk8s/readiness-check:2.0.0 Image ID: docker-pullable://oomk8s/readiness-check@sha256:7daa08b81954360ad03364febcb3dcfeb723bcc12ce3eb3ed3e53f2323ed Port: Host Port: Command: /root/ready.py Args: --container-name sdc-cs State: Terminated Reason: Completed Exit Code:0 Started: Sat, 01 Dec 2018 12:34:16 + Finished: Sat, 01 Dec 2018 12:35:18 + Ready: True Restart Count: 0 Environment: NAMESPACE: onap (v1:metadata.namespace) Mounts: /var/run/secrets/kubernetes.io/serviceaccount from default-token-zfhz6 (ro) Containers: sdc-cs-job: Container ID: docker://9dadbf63310313578e5090d24a87a87bddcaa1c8587ae125bb526723a3704b59 Image: nexus3.onap.org:10001/onap/sdc-cassandra-init:1.3.5 Image ID: docker-pullable://nexus3.onap.org:10001/onap/sdc-cassandra-init@
Re: [onap-discuss] onap/values.yaml customization #oom
Hi,
You can take a look at:
https://gerrit.onap.org/r/gitweb?p=integration.git;a=blob;f=deployment/heat/onap-oom/env/windriver/onap-oom.env;h=dccfed8ce521ec72bec6c033d294904a20ed9f14;hb=refs/heads/master
There are parameters that receive values in integration lab.
Probably integration team can expand on this.
The interesting part in this file is:
global:
repository: __docker_proxy__
pullPolicy: IfNotPresent
robot:
flavor: large
appcUsername: "a...@appc.onap.org"
appcPassword: "demo123456!"
openStackKeyStoneUrl: "http://10.12.25.2:5000;
openStackPublicNetId: "__public_net_id__"
openStackTenantId: "${OS_PROJECT_ID}"
openStackUserName: "${OS_USERNAME}"
ubuntu14Image: "ubuntu-14-04-cloud-amd64"
ubuntu16Image: "ubuntu-16-04-cloud-amd64"
openStackPrivateNetId: "__oam_network_id__"
openStackPrivateSubnetId: "__oam_subnet_id__"
openStackPrivateNetCidr: "__oam_network_cidr__"
openStackSecurityGroup: "__sec_group__"
openStackOamNetworkCidrPrefix: "10.0"
dcaeCollectorIp: "__k8s_1_vm_ip__"
vnfPubKey: "ssh-rsa
B3NzaC1yc2EDAQABAAABAQDKXDgoo3+WOqcUG8/5uUbk81+yczgwC4Y8ywTmuQqbNxlY1oQ0YxdMUqUnhitSXs5S/yRuAVOYHwGg2mCs20oAINrP+mxBI544AMIb9itPjCtgqtE2EWo6MmnFGbHB4Sx3XioE7F4VPsh7japsIwzOjbrQe+Mua1TGQ5d4nfEOQaaglXLLPFfuc7WbhbJbK6Q7rHqZfRcOwAMXgDoBqlyqKeiKwnumddo2RyNT8ljYmvB6buz7KnMinzo7qB0uktVT05FH9Rg0CTWH5norlG5qXgP2aukL0gk1ph8iAt7uYLf1ktp+LJI2gaF6L0/qli9EmVCSLr1uJ38Q8CBflhkh"
demoArtifactsVersion: "1.3.0-SNAPSHOT"
scriptVersion: "1.3.0-SNAPSHOT"
rancherIpAddress: "__rancher_ip_addr__"
config:
openStackEncryptedPasswordHere: "${OS_PASSWORD_ENCRYPTED}"
so:
so-openstack-adapter:
config:
openStackUserName: "${OS_USERNAME}"
openStackKeyStoneUrl: "http://10.12.25.2:5000/v2.0;
openStackEncryptedPasswordHere: "${OS_PASSWORD_ENCRYPTED}"
appc:
replicaCount: 1
config:
enableClustering: false
enableAAF: true
openStackType: "OpenStackProvider"
openStackName: "OpenStack"
openStackKeyStoneUrl: "http://10.12.25.2:5000/v2.0;
openStackServiceTenantName: "${OS_PROJECT_NAME}"
openStackDomain: "${OS_USER_DOMAIN_NAME}"
openStackUserName: "${OS_USERNAME}"
openStackEncryptedPassword: "${OS_PASSWORD}"
sdnc:
replicaCount: 1
config:
enableClustering: false
Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726
[amdocs-a]
Amdocs a Platinum member of
ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap>
From: onap-discuss@lists.onap.org On Behalf Of
gulsumat...@gmail.com
Sent: Wednesday, November 7, 2018 4:51 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] onap/values.yaml customization #oom
Hello,
In /oom/kubernetes/onap/values.yaml file; 3 modules(appc, nbi, so )
includes the openstack related parameters. Which parameters are
required to be customized and how can we do it ?
I couln't find clear explanation regarding with this file. It would be
very useful if there is any example configuration.
Thanks a lot.
appc:
enabled: true
config:
openStackType: OpenStackProvider
openStackName: OpenStack
openStackKeyStoneUrl: http://localhost:8181/apidoc/explorer/index.html
openStackServiceTenantName: default
openStackDomain: default
openStackUserName: admin
openStackEncryptedPassword: admin
nbi:
enabled: true
config:
# openstack configuration
openStackRegion: "Yolo"
openStackVNFTenantId: "1234"
so:
enabled: true
replicaCount: 1
liveness:
# necessary to disable liveness probe when setting breakpoints
# in debugger so K8s doesn't restart unresponsive container
enabled: true
# so server configuration
config:
# message router configuration
dmaapTopic: "AUTO"
# openstack configuration
openStackUserName: "vnf_user"
openStackRegion: "RegionOne"
openStackKeyStoneUrl: "http://1.2.3.4:5000<http://1.2.3.4:5000/>"
openStackServiceTenantName: "service"
openStackEncryptedPasswordHere: "b51fd164d68bdf2ef9fr94gvtrlk4jkgbr"
# configure embedded mariadb
mariadb:
config:
mariadbRootPassword: password
“Amdocs’ email platform is based on a third-party, worldwide, cloud-based
system. Any emails sent to Amdocs will be processed and stored using such
system and are accessible by third party providers of such system on a limited
basis. Your sending of emails to Amdocs evidences your consent to the use of
such system and such processing, storing and access”.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13587): https://lists.onap.org/g/onap-discuss/message/13587
Mute This Topic: https://lists.onap.org/mt/28023407/21656
Mute #oom: https://lists.onap.org/mk?hashtag=oom=2740164
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] [OOM] Not able to deploy ONAP using OOM master
Hi,
Please take a look at previous emails on OOM installation and also at this link:
https://wiki.onap.org/display/DW/OOM+Helm+%28un%29Deploy+plugins
Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726
[amdocs-a]
Amdocs a Platinum member of
ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap>
From: onap-discuss@lists.onap.org On Behalf Of
subhash kumar singh
Sent: Monday, October 22, 2018 5:26 PM
To: onap-discuss
Cc: Seshu m ; Kanagaraj Manickam
Subject: [onap-discuss] [OOM] Not able to deploy ONAP using OOM master
Hello Everyone,
I am using master OOM to deploy ONAP by following the latest documentation [1]
but I am not able to deploy ONAP. I observed that exception is thrown because
of configMap size in tiller logs.
Same issue is reported in jira [2] and it is closed.Could you please let me
know if I have to add some steps to deploy ONAP using OOM.
Following are logs :
$ helm install local/onap -n dev --namespace onap --debug
[debug] Created tunnel using local port: '45279'
[debug] SERVER: "127.0.0.1:45279"
[debug] Original chart version: ""
[debug] Fetched local/onap to /home/ubuntu/.helm/cache/archive/onap-3.0.0.tgz
[debug] CHART PATH: /home/ubuntu/.helm/cache/archive/onap-3.0.0.tgz
Error: release dev failed: Deployment in version "v1beta1" cannot be handled as
a Deployment: v1beta1.Deployment: Spec: v1beta1.DeploymentSpec: Template:
v1.PodTemplateSpec: Spec: v1.PodSpec: Containers:$
[]v1.Container: v1.Container: Env: []v1.EnvVar: v1.EnvVar: Value: ReadString:
expects " or n, but found 8, error found in #10 byte of
...|,"value":8089},{"nam|..., bigger context ...|ainers":[{"env":[{"na
me":"EXTERNAL_PORT","value":8089},{"name":"MSB_ADDR","value":"msb-iag:80"}],"im|...
logs from tiller pod:
2018/10/22 14:09:42 info: manifest
"onap/charts/vid/charts/vid_mariadb_galera/templates/pvc.yaml" is empty.
Skipping.
[tiller] 2018/10/22 14:09:43 performing install for dev
[tiller] 2018/10/22 14:09:43 executing 0 pre-install hooks for dev
[tiller] 2018/10/22 14:09:43 hooks complete for pre-install dev
[storage] 2018/10/22 14:09:43 getting release history for "dev"
[storage] 2018/10/22 14:09:43 creating release "dev.v1"
[storage/driver] 2018/10/22 14:09:45 create: failed to create: ConfigMap
"dev.v1" is invalid: []: Too long: must have at most 1048576 characters
[tiller] 2018/10/22 14:09:45 warning: Failed to record release dev: ConfigMap
"dev.v1" is invalid: []: Too long: must have at most 1048576 characters
[kube] 2018/10/22 14:09:45 building resources from manifest
[kube] 2018/10/22 14:09:46 creating 732 resource(s)
[tiller] 2018/10/22 14:10:01 warning: Release "dev" failed: Deployment in
version "v1beta1" cannot be handled as a Deployment: v1beta1.Deployment: Spec:
v1beta1.DeploymentSpec: Template: v1.PodTemplateSpec: Spec: v1.PodSpec:
Containers: []v1.Container: v1.Container: Env: []v1.EnvVar: v1.EnvVar: Value:
ReadString: expects " or n, but found 8, error found in #10 byte of
...|,"value":8089},{"nam|..., bigger context
...|ainers":[{"env":[{"name":"EXTERNAL_PORT","value":8089},{"name":"MSB_ADDR","value":"msb-iag:80"}],"im|...
[storage] 2018/10/22 14:10:01 updating release "dev.v1"
[storage/driver] 2018/10/22 14:10:06 update: failed to update: configmaps
"dev.v1" not found
[tiller] 2018/10/22 14:10:06 warning: Failed to update release dev: configmaps
"dev.v1" not found
[tiller] 2018/10/22 14:10:06 failed install perform step: release dev failed:
Deployment in version "v1beta1" cannot be handled as a Deployment:
v1beta1.Deployment: Spec: v1beta1.DeploymentSpec: Template: v1.PodTemplateSpec:
Spec: v1.PodSpec: Containers: []v1.Container: v1.Container: Env: []v1.EnvVar:
v1.EnvVar: Value: ReadString: expects " or n, but found 8, error found in #10
byte of ...|,"value":8089},{"nam|..., bigger context
...|ainers":[{"env":[{"name":"EXTERNAL_PORT","value":8089},{"name":"MSB_ADDR","value":"msb-iag:80"}],"im|...
[storage] 2018/10/22 14:11:57 listing all releases with filter
[1]
https://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_setup_kubernetes_rancher.htm
[2] https://jira.onap.org/browse/OOM-858
--
Regards,
Subhash Kumar Singh
FNOSS, ONAP
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka
Tel: + 91-80-49160700 Ext 70992 II Mob: 8050101106 Email:
subhash.kumar.si...@huawei.com<mailto:a...@huawei.com>
[cid:image002.jpg@01D46AE8.67B63BA0]
This e-mail and its at
Re: [onap-discuss] [OOM] Referencing a job name from another chart
Hi,
The job aaf-sms-preload should have no Release.Name in its name
Oof should look for that job without Release.Name either. Since there are no
other jobs with same name in this namespace, this will work.
Usage of Release.Name should be minimal and only when completely necessary
(like in case of sharing configuration between different charts of same
component, and even then it is a stretch).
Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726
[amdocs-a]
Amdocs a Platinum member of
ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap>
From: onap-discuss@lists.onap.org On Behalf Of
Kiran Kamineni
Sent: Wednesday, October 17, 2018 2:28 AM
To: Ranganathan, Dileep ;
onap-discuss@lists.onap.org; Michael O'Brien
Subject: Re: [onap-discuss] [OOM] Referencing a job name from another chart
This is an issue in situations where we are using helm deploy for bringing up
oof.
Using helm install in the same helm release will not run into this issue.
-- K i r a n
From: Ranganathan, Dileep
Sent: Tuesday, October 16, 2018 3:44 PM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>;
frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>
Cc: Kamineni, Kiran K
mailto:kiran.k.kamin...@intel.com>>
Subject: [OOM] Referencing a job name from another chart
Hi,
In the deployment.yaml of oof,. we need to wait till the job aaf-sms-preload
(defined inside aaf-sms subcharts) using job_complete.py. I tried to use {{
.Release.Name }}-aaf-sms-preload to get the name but since it is in a different
project, it is failing. Is there any way we can refer a job defined in another
chart?
Thanks,
Dileep
“Amdocs’ email platform is based on a third-party, worldwide, cloud-based
system. Any emails sent to Amdocs will be processed and stored using such
system and are accessible by third party providers of such system on a limited
basis. Your sending of emails to Amdocs evidences your consent to the use of
such system and such processing, storing and access”.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13096): https://lists.onap.org/g/onap-discuss/message/13096
Mute This Topic: https://lists.onap.org/mt/27374675/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] [OOM] StatefulSet not removed while Delete/Purge a project
When I purge the project, I usually do “kubectl delete namespace ” and it takes care of most resources. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: onap-discuss@lists.onap.org On Behalf Of Kiran Kamineni Sent: Thursday, October 11, 2018 12:53 AM To: Ranganathan, Dileep ; onap-discuss@lists.onap.org; Mandeep Khinda ; Michael O'Brien ; NELSON JR., THOMAS ; PUZHAVAKATH NARAYANAN, SHANKARANARAYANAN Subject: Re: [onap-discuss] [OOM] StatefulSet not removed while Delete/Purge a project It seems that the pods have some lifecycle hooks on them. These are blocking by default. They will need to complete before the call to delete the pod can be sent. Maybe they are not completing or there is some other error there. In the case of the cassandra pod, it seems like we have a preStop that seems to want to do a graceful shutdown of the process: ["/bin/sh", "-c", "PID=$(pidof java) && kill $PID && while ps -p $PID > /dev/null; do sleep 1; done"] Why not use nodetool drain instead of kill as documented here (https://kubernetes.io/docs/tutorials/stateful-application/cassandra/ ) Thanks, -- K i r a n From: Ranganathan, Dileep Sent: Wednesday, October 10, 2018 9:13 AM To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; mandeep.khi...@amdocs.com<mailto:mandeep.khi...@amdocs.com>; Michael O'Brien mailto:frank.obr...@amdocs.com>>; Kamineni, Kiran K mailto:kiran.k.kamin...@intel.com>>; NELSON JR., THOMAS mailto:tn1...@att.com>>; PUZHAVAKATH NARAYANAN, SHANKARANARAYANAN mailto:snaraya...@research.att.com>> Subject: RE: [onap-discuss] [OOM] StatefulSet not removed while Delete/Purge a project I am having helm version of 2.9.1 and k8s 1.8.x When we purge the project, do we have to do something extra to make sure the common chart resources get purged as well? From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> [mailto:onap-discuss@lists.onap.org] On Behalf Of Mandeep Khinda Sent: Wednesday, October 10, 2018 7:11 AM To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; Ranganathan, Dileep mailto:dileep.ranganat...@intel.com>>; Michael O'Brien mailto:frank.obr...@amdocs.com>>; Kamineni, Kiran K mailto:kiran.k.kamin...@intel.com>>; NELSON JR., THOMAS mailto:tn1...@att.com>>; PUZHAVAKATH NARAYANAN, SHANKARANARAYANAN mailto:snaraya...@research.att.com>> Subject: Re: [onap-discuss] [OOM] StatefulSet not removed while Delete/Purge a project Hi Dileep, What version of helm & kubernetes are you using? In Casablanca we have up-revved the recommended helm 2.9.1 and K8s 1.10.x There are some known issues where dynamic PVC resources are left behind after a purge but not statefulsets. From: mailto:onap-discuss@lists.onap.org>> on behalf of Dileep Ranganathan mailto:dileep.ranganat...@intel.com>> Reply-To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" mailto:onap-discuss@lists.onap.org>>, "dileep.ranganat...@intel.com<mailto:dileep.ranganat...@intel.com>" mailto:dileep.ranganat...@intel.com>> Date: Wednesday, October 10, 2018 at 12:15 AM To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" mailto:onap-discuss@lists.onap.org>>, Michael O'Brien mailto:frank.obr...@amdocs.com>>, "Kamineni, Kiran K" mailto:kiran.k.kamin...@intel.com>>, "NELSON JR., THOMAS" mailto:tn1...@att.com>>, "PUZHAVAKATH NARAYANAN, SHANKARANARAYANAN" mailto:snaraya...@research.att.com>> Subject: [onap-discuss] [OOM] StatefulSet not removed while Delete/Purge a project Hi OOM team, For the OOF project, while deleting/purging a project, there are some dangling resources which is affecting redeploy. OOF has added common music charts in requirements.yaml (WIP) and it is starting Cassandra and Zookeeper. The statefulsets and pods related to these two services brought up as part of common charts are not deleted while deleting the project oof. These are the steps I am following to redeploy oof in my local system. helm del dev-oof –purge helm deploy dev local/onap --namespace onap And the error I am getting is. Release "dev-oof" does not exist. Installing it now. Error: release dev-oof failed: statefulsets.apps "dev-oof-cassandra" already exists Thanks, Dileep 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 “Amdocs’ email platform is based on a third-party, worldwide, cloud-based system. Any emails sent to Amdocs will be processed and stored using such system and are accessible by third
Re: [onap-discuss] [integration] Benchmark issue: ONAP deployment using OOM
Hi, It is not clear what you mean by “all services are in one physical server”. ONAP using OOM should be able to be installed on any kubernetes (assuming it is version 1.8.10 and higher), but it was tested with Rancher k8s on Windriver Openstack in integration. (also in other labs…) I know ONAP was deployed on Azure and AWS. It should be possible to deploy ONAP using OOM without openstack (baremetal?). However in order to run the tests (vFW etc.) you need an Openstack accessible from your k8s deployment. Please try and share results with the community… Thanks, Borislav Glozman O:+972.9.776.1988 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On Behalf Of Hongliang Bian Sent: Thursday, September 13, 2018 6:24 AM To: onap-discuss@lists.onap.org Subject: [onap-discuss] [integration] Benchmark issue: ONAP deployment using OOM Hi, all, We are trying to deploy ONAP using OOM. Since all services are in one physical server in OOM, we want to know if we still need openstack when deploying ONAP using OOM? Thanks:) 卞宏梁/Bian Hongliang 中国电信股份有限公司北京研究院/China Telecom Corporation Limited Beijing Research Institute 昌平区北七家镇未来科技城南区中国电信北京信息科技创新园，邮编：102209 China Telecom Beijing Information Science & Technology Innovation Park, Southern Zone of Future Science & Technology City, Beiqijia Town, Changping District, Beijing, 102209, China TEL： +86 010-5090-2955 E-mail： bianhl@chinatelecom.cn<mailto:bia...@ctbri.com.cn> “Amdocs’ email platform is based on a third-party, worldwide, cloud-based system. Any emails sent to Amdocs will be processed and stored using such system and are accessible by third party providers of such system on a limited basis. Your sending of emails to Amdocs evidences your consent to the use of such system and such processing, storing and access”. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12418): https://lists.onap.org/g/onap-discuss/message/12418 Mute This Topic: https://lists.onap.org/mt/25616130/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] onap common component installation problem
Hi, You do not need to install local/common. This is a collection of charts that other charts use and install when they are installed. Thanks, Borislav Glozman O:+972.9.776.1988 Amdocs a Platinum member of ONAP -Original Message- From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On Behalf Of Rudolf Amirjanyan Sent: Saturday, September 1, 2018 10:24 PM To: onap-discuss@lists.onap.org Subject: [onap-discuss] onap common component installation problem Hello All, Installing ONAP components one by one and when i am performing I get error --> Error: release common-bbb failed: no objects visited Please help me understand why it happened Thanks, Rudolf -- “Amdocs’ email platform is based on a third-party, worldwide, cloud-based system. Any emails sent to Amdocs will be processed and stored using such system and are accessible by third party providers of such system on a limited basis. Your sending of emails to Amdocs evidences your consent to the use of such system and such processing, storing and access”. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12198): https://lists.onap.org/g/onap-discuss/message/12198 Mute This Topic: https://lists.onap.org/mt/25150489/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] Question about ONAP installation
Take a look at charts deployment.yaml, statefulset.yaml, job.yaml etc. and look
for init-container.
There are readiness containers that are expressing the dependencies.
Example:
dcaegen2/charts/dcae-bootstrap/templates/job.yaml
initContainers:
- name: {{ include "common.name" . }}-readiness
image: {{ .Values.global.readinessRepository }}/{{
.Values.global.readinessImage }}
imagePullPolicy: {{ .Values.global.pullPolicy | default
.Values.pullPolicy }}
command:
- /root/ready.py
args:
- --container-name
- dcae-cloudify-manager
- --container-name
- consul-server
- --container-name
- msb-discovery
- --container-name
- kube2msb
- "-t"
- "15"
>From this I learn that dcae depends on consul and msb components.
Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726
Amdocs a Platinum member of ONAP
-Original Message-
From: Rudolf Amirjanyan [mailto:rud...@data.co.ug]
Sent: Thursday, August 16, 2018 5:40 PM
To: onap-discuss@lists.onap.org; Borislav Glozman
Subject: Re: [onap-discuss] Question about ONAP installation
Thanks Borislav for your promt responce.
the second option is really very useful.
But I have second question actually :).
How to know which components depends on which , so I would deploy them too ?
Regards,
Rudolf
On 08/16/2018 04:44 PM, Borislav Glozman wrote:
> Hi Rudolf,
>
> You would also need to run "make all" after the change.
>
> As another option, you can run
> helm upgrade -i --namespace onap -f
> onap/resources/environments/disable-allcharts.yaml --set
> portal.enabled=true,so.enabled=true
>
> If the component you would like to deploy depends on other components, you
> would need to deploy them as well.
>
>
> Thanks,
> Borislav Glozman
> O:+972.9.776.1988
> M:+972.52.2835726
>
> Amdocs a Platinum member of ONAP
>
> -Original Message-
> From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On
> Behalf Of Rudolf Amirjanyan
> Sent: Thursday, August 16, 2018 2:46 PM
> To: onap-discuss@lists.onap.org
> Subject: [onap-discuss] Question about ONAP installation
>
> Hello All,
>
> Installing ONAP on kubernetes using OOM.
>
> Question is following:
>
> If I change the onap/values.yaml file and set "false" for all onap components
> (sdc, sdnc, robot, etc), except one (for example PORTAL) and run -->
>
> helm install local/onap --name dev --namespace onap
>
> In that case will the only component be installed successfully or it will be
> failed because of dependencies ?
>
> Thanks,
>
> Rudolf
>
--
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
<https://www.amdocs.com/about/email-disclaimer>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11907): https://lists.onap.org/g/onap-discuss/message/11907
Mute This Topic: https://lists.onap.org/mt/24569917/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] Question about ONAP installation
Hi Rudolf, You would also need to run "make all" after the change. As another option, you can run helm upgrade -i --namespace onap -f onap/resources/environments/disable-allcharts.yaml --set portal.enabled=true,so.enabled=true If the component you would like to deploy depends on other components, you would need to deploy them as well. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 Amdocs a Platinum member of ONAP -Original Message- From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On Behalf Of Rudolf Amirjanyan Sent: Thursday, August 16, 2018 2:46 PM To: onap-discuss@lists.onap.org Subject: [onap-discuss] Question about ONAP installation Hello All, Installing ONAP on kubernetes using OOM. Question is following: If I change the onap/values.yaml file and set "false" for all onap components (sdc, sdnc, robot, etc), except one (for example PORTAL) and run --> helm install local/onap --name dev --namespace onap In that case will the only component be installed successfully or it will be failed because of dependencies ? Thanks, Rudolf -- 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 <https://www.amdocs.com/about/email-disclaimer> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11901): https://lists.onap.org/g/onap-discuss/message/11901 Mute This Topic: https://lists.onap.org/mt/24569917/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] setting up local repository for OOM images
I am not aware of such document, I know integration team did that. Adding Gary. You do not need to change the yaml file. You can provide parameter to helm install/upgrade "--set global.repository=mynexus3.example.com:12345" that will override the default docker image registry (nexus3.onap.org:10001). Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: Vidhu Shekhar Pandey - ERS, HCL Tech [mailto:vidhu.pan...@hcl.com] Sent: Thursday, August 16, 2018 9:55 AM To: Borislav Glozman Cc: onap-discuss@lists.onap.org; Mike Elliott ; Michael O'Brien Subject: RE: setting up local repository for OOM images Hi Borislav, Is there a document for setting up nexus3 that I can follow. What modifications will be required in OOM charts/values.yaml to point to local repository? I hope I won't have to change it in all yaml files for each component? Thanks, Vidhu From: Borislav Glozman mailto:borislav.gloz...@amdocs.com>> Sent: 16 August 2018 12:17 To: Vidhu Shekhar Pandey - ERS, HCL Tech mailto:vidhu.pan...@hcl.com>> Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; Mike Elliott mailto:mike.elli...@amdocs.com>>; Michael O'Brien mailto:frank.obr...@amdocs.com>> Subject: RE: setting up local repository for OOM images Hi, You can set a local nexus3 server that would proxy and cache the images. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.amdocs.com%2Fopen-network%2Fnfv-powered-by-onap=02%7C01%7Cvidhu.pandey%40hcl.com%7C77d3deff6d1a40cca66308d603441bec%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636699988404349594=2o0joUpsUSF6aD3N2ksOnB%2BuMsxnEws6dPQygJ0DjSs%3D=0> From: Vidhu Shekhar Pandey - ERS, HCL Tech [mailto:vidhu.pan...@hcl.com] Sent: Thursday, August 16, 2018 5:56 AM To: Borislav Glozman mailto:borislav.gloz...@amdocs.com>> Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; Mike Elliott mailto:mike.elli...@amdocs.com>>; Michael O'Brien mailto:frank.obr...@amdocs.com>> Subject: setting up local repository for OOM images Hi Borislav, I want to avoid re-pulling all the images every time from nexus repository. I there a way to host a local repository of images for installing OOM Beijing? Regards, Vidhu ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- 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<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.amdocs.com%2Fabout%2Femail-disclaimer=02%7C01%7Cvidhu.pandey%40hcl.com%7C77d3deff6d1a40cca66308d603441bec%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636699988404359599=uG8hdmq1pOQYGeB0HaF6aqQZMqN%2FhV8YfpQxy0Lpqic%3D=0> 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 <https://www.amdocs.com/about/email-disclaimer> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11896): https://lists.onap.org/g/on
Re: [onap-discuss] setting up local repository for OOM images
Hi, You can set a local nexus3 server that would proxy and cache the images. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: Vidhu Shekhar Pandey - ERS, HCL Tech [mailto:vidhu.pan...@hcl.com] Sent: Thursday, August 16, 2018 5:56 AM To: Borislav Glozman Cc: onap-discuss@lists.onap.org; Mike Elliott ; Michael O'Brien Subject: setting up local repository for OOM images Hi Borislav, I want to avoid re-pulling all the images every time from nexus repository. I there a way to host a local repository of images for installing OOM Beijing? Regards, Vidhu ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- 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 <https://www.amdocs.com/about/email-disclaimer> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11895): https://lists.onap.org/g/onap-discuss/message/11895 Mute This Topic: https://lists.onap.org/mt/24568685/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] [oom] Weekly Meeing: Hi there, ONAP Meeting 5 is inviting you to a scheduled Zoom meeting. Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/118908904Or iPhone one-tap (US
Hi, Seems there is a problem with zoom. I am getting a message "The host has another meeting in progress". Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [cid:image002.jpg@01D38FAC.4D03D500] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> -Original Appointment- From: ONAP Meetings and Events [mailto:linuxfoundation.org_1rmtb5tpr3uc8f76fmflplo...@group.calendar.google.com] Sent: None To: ONAP Meetings and Events; david.sauvag...@bell.ca; onap-discuss@lists.onap.org; Borislav Glozman Subject: [oom] Weekly Meeing: Hi there, ONAP Meeting 5 is inviting you to a scheduled Zoom meeting. Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/118908904Or iPhone one-tap (US Toll): +14086380968,,118908904# or +16465588656,,118908904#Or Telephone: When: Wednesday, July 25, 2018 7:00 AM-8:00 AM America/Los_Angeles. Where: https://zoom.us/j/118908904 Hi there, ONAP Meeting 5 is inviting you to a scheduled Zoom meeting. Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/118908904 Or iPhone one-tap (US Toll): +14086380968,,118908904# or +16465588656,,118908904# Or Telephone: Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll) +1 855 880 1246 (US Toll Free) +1 877 369 0926 (US Toll Free) Meeting ID: 118 908 904 International numbers available: https://zoom.us/zoomconference?m=RjcDSzvXlwMWG5gaHA7q936bD1fmNWjr 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 <https://www.amdocs.com/about/email-disclaimer> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11414): https://lists.onap.org/g/onap-discuss/message/11414 Mute This Topic: https://lists.onap.org/mt/23812967/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=- <>
Re: [onap-discuss] How to access esr-gui in OOM deployment
Thanks for the explanation! Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: li.z...@zte.com.cn [mailto:li.z...@zte.com.cn] Sent: Wednesday, July 25, 2018 3:53 AM To: Borislav Glozman Cc: onap-discuss@lists.onap.org; aroraa...@vmware.com; Sudhakar Reddy Subject: Re: [onap-discuss] How to access esr-gui in OOM deployment Hi Borislav, Actually, this is not a bug for ESR. ESR will register to MSB before it can be in use. The ESR portal should be visited from MSB node IP and nodePort. , That is why ESR not expose the nodePort of itself. Thanks, LiZi 原始邮件 发件人：BorislavGlozman mailto:borislav.gloz...@amdocs.com>> 收件人：onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> mailto:onap-discuss@lists.onap.org>>aroraa...@vmware.com<mailto:aroraa...@vmware.com> mailto:aroraa...@vmware.com>>Sudhakar Reddy mailto:sudhakar.re...@amdocs.com>> 日 期 ：2018年07月24日 22:51 主 题 ：Re: [onap-discuss] How to access esr-gui in OOM deployment Hi, Indeed in Beijing OOM esr is defined in values.yaml as: service: name: esr internalPort: 9518 This means it is not exposed as NodePort and cannot be accessed from outside the cluster without manipulations. Please raise this as a bug and esr team is welcome to fix this. Please notice that port 30280 is already taken by msb. Need to allocate another port according to: https://wiki.onap.org/display/DW/OOM+NodePort+List Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> [mailto:onap-discuss@lists.onap.org] On Behalf Of Arun Arora Sent: Tuesday, July 24, 2018 11:03 AM To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; Sudhakar Reddy mailto:sudhakar.re...@amdocs.com>> Subject: Re: [onap-discuss] How to access esr-gui in OOM deployment Didn’t need to do anything else. For me following worked: http://http://%3ck8s> node IP>:30280/iui/aai-esr-gui/extsys/vim/vimView.html Best Regards, Arun Arora From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> [mailto:onap-discuss@lists.onap.org] On Behalf Of Sudhakar Reddy Sent: 24 July 2018 10:38 To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: Re: [onap-discuss] How to access esr-gui in OOM deployment Hi, Service port is not exposed in esr-gui due to which you are not able to access the GUI.But if you are using Amsterdam relase of ONAP, you can access it using the below url from Portal VNC http://:8080/iui/aai-esr-gui/extsys/vim/vimView.html<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2F40.71.213.204%3A30080%2Fiui%2Faai-esr-gui%2Fextsys%2Fvim%2FvimView.html=02%7C01%7Caroraarun%40vmware.com%7C5f4a3279af9a4023482908d5f1236302%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C636680056654334438=dx4NNe4%2BSBhR9Hgthj13um5PAnzMxP0ou6vEdCuAnq4%3D=0> If you are working on latest version of ONAP, then you need to expose the 8080 port to access. This can be changed in your service.yaml file of esr-gui. 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 <https://www.amdocs.com/about/email-disclaimer> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11406): https://lists.onap.org/g/onap-discuss/message/11406 Mute This Topic: https://lists.onap.org/mt/23792624/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] facing problem with portal app
Hi, The AAF problem is usually related to nfs (/dockerdata-nfs) not working between the nodes. Please check that the nfs is working. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: Michael O'Brien Sent: Thursday, July 19, 2018 5:49 PM To: Vidhu Shekhar Pandey - ERS, HCL Tech ; Borislav Glozman ; Mike Elliott Cc: onap-discuss@lists.onap.org Subject: RE: facing problem with portal app Hi, For the aaf pod - this looks like one of the known issue pods - we need a page for these though for reference - the teams like AAF can keep up to date (along with checking the status of the CI/CD reference servers) For your portal issue - I don't remember if it was your team or another we were working with - where I mentioned that only the Rancher RI comes with a default LoadBalancer service - make sure if you are using an alternative kubernetes setup based on kubectl that you setup your own native LoadBalancer - or switch to using Rancher. Thank you /michael From: Vidhu Shekhar Pandey - ERS, HCL Tech mailto:vidhu.pan...@hcl.com>> Sent: Thursday, July 19, 2018 10:08 AM To: Michael O'Brien mailto:frank.obr...@amdocs.com>>; Borislav Glozman mailto:borislav.gloz...@amdocs.com>>; Mike Elliott mailto:mike.elli...@amdocs.com>> Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: RE: facing problem with portal app Hi Mike/Borislav, As discussed in yesterday's meeting I am sharing the configuration I have setup in my lab. I have one Rancher node and a cluster of 4 Kubernetes nodes for the Beijing release. Rancher VM is 12 vCPU, 15GB RAM , 80GB disk. Each k8s VM node is 12 vCPUs, 40GB RAM, 160GB disk. This I am setting this up in OpenStack following the steps is link http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_setup_kubernetes_rancher.html<https://apac01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fonap.readthedocs.io%2Fen%2Flatest%2Fsubmodules%2Foom.git%2Fdocs%2Foom_setup_kubernetes_rancher.html=02%7C01%7Cvidhu.pandey%40hcl.com%7C72d034dbb53f4dd2c42c08d5e205a0ca%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636663436181210425=QdyQWTZpRsQQ2bdilKXCrBKk7ydFYhMfkArzo4A%2BQNM%3D=0>. I had shared this with Michael O'Brien earlier and got the setup verified as in the below mail. But even after trying 2-3 attempts some of the pods did not come up. These are intermittent and the failed pods vary each time. In recent run I had problem with: onap-aaf-cm (crashloopbackoff) onap-dbc-pg-0 (this shows readiness probe failure) onap-dbc-pg-1 (this pod used to come up earlier but not this time) onap-dmaap-bus-controller (crashloopbackoff) portal-app (this remains in init state every time due to a failed init container) Just wanted to know if having 6 k8s nodes with 32 GB RAM, as suggested by Borislav in recent posts, would improve the chances? Michael had indicated that there are Docker image downloading problems which can lead to pod syncing issues. What Internet speed is recommended for pulling the images; could fluctuating bandwidth be a problem? Thanks, Vidhu From: Michael O'Brien [mailto:frank.obr...@amdocs.com] Sent: 05 July 2018 04:57 To: Vidhu Shekhar Pandey - ERS, HCL Tech mailto:vidhu.pan...@hcl.com>> Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: RE: facing problem with portal app Adding ONAP community for reference and input Your setup looks fine - docker downloads will be 40G per VM, the master will only run the rancher/kubernetes system, ONAP will sort of come up in 96G but it will expand past 120G if you provide a large enough cluster - you are running 160G so ok there as well. Deploying ONAP on a clean set of VM will be problematic mostly because of the docker downloads issue - until we retrofit the preload script to run off the manifest. The 2nd time you deploy it will come up faster for that day as your 4 docker caches per/vm are filled. This is less of a problem on some cloud providers and if you run behind your own local nexus3 proxy. The NFS share is recommended but not required until pods start getting rescheduled across cluster VM's The system does have dependency tracking in the case of readiness checks - but the number of retries are unfortunately finite in number and durations and start time - to be fine tuned as we go. Therefore you are subject to a bit of random start order for now - as we have not allocated resource cpu/ram where it is required low in the dep tree yet - except for DaemonSets. Lately for the past 2 weeks portal has also been failing for the CD system when it runs every 4 hours, along with clamp, appc, nbi, oof, policy, sdc (db init container related retries), sdnc, so, and intermittently dcae, aaf, and a couple aai on kibana.onap.info:5601 I have not looked into all of these f
Re: [onap-discuss] [oom]OOM Beijing Jenkins Jobs
Thanks Gary! I understand the correct links are: https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-oom-daily/ https://jenkins.onap.org/view/External%20Labs/job/lab-tlab-oom-daily/ Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: Gary Wu [mailto:gary.i...@huawei.com] Sent: Wednesday, July 18, 2018 7:44 PM To: onap-discuss@lists.onap.org; Borislav Glozman ; bharath.thiruveed...@verizon.com Cc: UdhayaChandran M ; Kumar Skand Priya, Viswanath V ; Parigi, Raghavender ; Yunxia Chen ; FREEMAN, BRIAN D Subject: RE: [onap-discuss] [oom]OOM Beijing Jenkins Jobs We’re no longer running daily deployment tests against the Beijing branch. All the testing have been switched to Casablanca. Thanks, Gary From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> [mailto:onap-discuss@lists.onap.org] On Behalf Of Borislav Glozman Sent: Wednesday, July 18, 2018 1:42 AM To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; bharath.thiruveed...@verizon.com<mailto:bharath.thiruveed...@verizon.com> Cc: UdhayaChandran M mailto:udhayachandra...@verizon.com>>; Kumar Skand Priya, Viswanath V mailto:viswanath.kumarskandpr...@verizon.com>>; Parigi, Raghavender mailto:raghavender.par...@one.verizon.com>>; Gary Wu mailto:gary.i...@huawei.com>>; Yunxia Chen mailto:helen.c...@huawei.com>>; FREEMAN, BRIAN D mailto:bf1...@att.com>> Subject: Re: [onap-discuss] [oom]OOM Beijing Jenkins Jobs Results used to be here: https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-oom-deploy/ But I see it is not running since 12/Jun. Adding integration team members, maybe you know whether it is supposed to continue running. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> [mailto:onap-discuss@lists.onap.org] On Behalf Of Bharath Thiruveedula via Lists.Onap.Org Sent: Wednesday, July 18, 2018 10:04 AM To: onap-discuss mailto:onap-discuss@lists.onap.org>> Cc: UdhayaChandran M mailto:udhayachandra...@verizon.com>>; Kumar Skand Priya, Viswanath V mailto:viswanath.kumarskandpr...@verizon.com>>; Parigi, Raghavender mailto:raghavender.par...@one.verizon.com>> Subject: [onap-discuss] [oom]OOM Beijing Jenkins Jobs Hi Can we see the status of jenkins oom deployment jobs somewhere? Previously I used to refer at http://jenkins.onap.info, but seems like it is not up now? Currently I am facing dmaap and aaf pods issues in different environments, so I just want to confirm with community about the pod status 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 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 <https://www.amdocs.com/about/email-disclaimer> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11233): https://lists.onap.org/g/onap-discuss/message/11233 Mute This Topic: https://lists.onap.org/mt/23659149/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] [oom]OOM Beijing Jenkins Jobs
Results used to be here: https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-oom-deploy/ But I see it is not running since 12/Jun. Adding integration team members, maybe you know whether it is supposed to continue running. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On Behalf Of Bharath Thiruveedula via Lists.Onap.Org Sent: Wednesday, July 18, 2018 10:04 AM To: onap-discuss Cc: UdhayaChandran M ; Kumar Skand Priya, Viswanath V ; Parigi, Raghavender Subject: [onap-discuss] [oom]OOM Beijing Jenkins Jobs Hi Can we see the status of jenkins oom deployment jobs somewhere? Previously I used to refer at http://jenkins.onap.info, but seems like it is not up now? Currently I am facing dmaap and aaf pods issues in different environments, so I just want to confirm with community about the pod status 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 <https://www.amdocs.com/about/email-disclaimer> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11204): https://lists.onap.org/g/onap-discuss/message/11204 Mute This Topic: https://lists.onap.org/mt/23659149/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] [OOM] SO port(s) not exposed #oom #so
It is not supposed to be exposed on host network. NodePort is exposed. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On Behalf Of DeWayne Filppi Sent: Tuesday, July 17, 2018 1:55 AM To: onap-discuss@lists.onap.org Subject: [onap-discuss] [OOM] SO port(s) not exposed #oom #so After doing the Helm install (Beijing branch) in my environment, I notice that port 8080 (jboss) isn't exposed on the host network, although all the Dockerfiles I've seen (and even elm) charts seem to expose it. Intentional? 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 <https://www.amdocs.com/about/email-disclaimer> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11166): https://lists.onap.org/g/onap-discuss/message/11166 Mute This Topic: https://lists.onap.org/mt/23536849/21656 Mute #oom: https://lists.onap.org/mk?hashtag=oom=2740164 Mute #so: https://lists.onap.org/mk?hashtag=so=2740164 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] [OOM] How to access Consul GUI
Could you please provide the exact errors? The representatives of the components that their health-checks are failing will be able to assist you. I think it would be better to send separate emails with those components in subject as [component] and the log of the failures. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On Behalf Of Arun Arora Sent: Friday, July 6, 2018 10:13 AM To: Borislav Glozman ; onap-discuss@lists.onap.org Subject: Re: [onap-discuss] [OOM] How to access Consul GUI Yes, It worked. Thanks. Now I can see some health-checks are failing. How to go about fixing them? Do I need to restart the pods? Best Regards, Arun Arora From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com] Sent: 06 July 2018 12:42 To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; Arun Arora (c) mailto:aroraa...@vmware.com>> Subject: Re: [onap-discuss] [OOM] How to access Consul GUI Hi, You can use ip of any of your k8s cluster nodes, port 30270. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 From: Arun Arora mailto:aroraa...@vmware.com>> Sent: Friday, July 6, 2018 09:27 To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: [onap-discuss] [OOM] How to access Consul GUI Hi everyone, I was able to successfully install ONAP (R2 release) and also able to access the portal. Before asking my query I would like to express my appreciation for the awesome documentation for the OOM based deployment. It really is very nice and meticulous. My query is, after deployment Consul UI is mentioned as preferred way for health-checks, but I didn't get exactly how to open the UI. In the snapshot it shows to be a WebUI and for that I ran the command to get the IP of consul pod, as similar thing was done to get the portal-app IP. Following is the output, and it does not seem to have a mapping with the and Rancher Node VM's IP. Could you please help me in understanding how to access the consul UI. root@rancher-node-1:~# kubectl -n onap get services|grep "consul" consul ExternalName consul-server.onap.svc.cluster.local 23h consul-server ClusterIP None 8301/TCP 23h consul-server-ui NodePort 10.43.185.78 8500:30270/TCP 23h msb-consul NodePort 10.43.51.159 8500:30285/TCP 23h root@rancher-node-1:~# Best Regards, Arun Arora 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<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.amdocs.com%2Fabout%2Femail-disclaimer=02%7C01%7Caroraarun%40vmware.com%7Cf2afa509ba8c4af1a3c708d5e30fb549%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C636664578973762511=MsqIdnYc12dwAU0JNc4%2BSh3GoewQ48BviwxwrEDUQ6I%3D=0> 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 <https://www.amdocs.com/about/email-disclaimer> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10943): https://lists.onap.org/g/onap-discuss/message/10943 Mute This Topic: https://lists.onap.org/mt/23171560/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] [OOM] How to access Consul GUI
Hi, You can use ip of any of your k8s cluster nodes, port 30270. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 From: Arun Arora Sent: Friday, July 6, 2018 09:27 To: onap-discuss@lists.onap.org Subject: [onap-discuss] [OOM] How to access Consul GUI Hi everyone, I was able to successfully install ONAP (R2 release) and also able to access the portal. Before asking my query I would like to express my appreciation for the awesome documentation for the OOM based deployment. It really is very nice and meticulous. My query is, after deployment Consul UI is mentioned as preferred way for health-checks, but I didn’t get exactly how to open the UI. In the snapshot it shows to be a WebUI and for that I ran the command to get the IP of consul pod, as similar thing was done to get the portal-app IP. Following is the output, and it does not seem to have a mapping with the and Rancher Node VM’s IP. Could you please help me in understanding how to access the consul UI. root@rancher-node-1:~# kubectl -n onap get services|grep "consul" consul ExternalName consul-server.onap.svc.cluster.local 23h consul-server ClusterIP None 8301/TCP 23h consul-server-ui NodePort 10.43.185.78 8500:30270/TCP 23h msb-consul NodePort 10.43.51.159 8500:30285/TCP 23h root@rancher-node-1:~# Best Regards, Arun Arora 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 <https://www.amdocs.com/about/email-disclaimer> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10915): https://lists.onap.org/g/onap-discuss/message/10915 Mute This Topic: https://lists.onap.org/mt/23171560/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] Getting cluster unavailable error if OOM is deployed in more than 1 node.
Hi Deepak, This is not enough. I am successfully running in cluster of 6 nodes of 32G RAM or 11 nodes of 16Gb RAM. For your consideration. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On Behalf Of Deepak S Sent: Thursday, July 5, 2018 8:46 AM To: Michael O'Brien ; onap-discuss@lists.onap.org Subject: Re: [onap-discuss] Getting cluster unavailable error if OOM is deployed in more than 1 node. Thanks Michael for the detailed answer. My setup has 2 k8s nodes with each around 50G RAM and a master node running rancher & the cluster was deployed using the scripts. kubectl get pods -all-namespaces -o wide: NAMESPACE NAMEREADY STATUS RESTARTS AGE IP NODE default beijing-aaf-cm-8448ddc4bf-z2lz6 0/1 Running 1 2d10.42.99.143oom default beijing-aaf-cs-5d4968ff8b-qcmxg 0/1 Running 0 2d10.42.211.8 oom default beijing-aaf-fs-6c7f5458db-694d6 1/1 Running 0 2d10.42.95.164oom default beijing-aaf-gui-64cd5c45dd-v2ghf1/1 Running 1 2d10.42.114.239 oom default beijing-aaf-hello-64cc6f9775-xlgx2 1/1 Running 1 2d10.42.198.193 oom default beijing-aaf-locate-746c4dbbf5-x6lxd 1/1 Running 0 2d10.42.177.144 oom default beijing-aaf-oauth-cbc4dd94-46bs70/1 Running 2 2d10.42.145.153 oom default beijing-aaf-service-7477475f78-25t490/1 Running 2 2d10.42.178.98oom default beijing-aaf-sms-674d5b9bdd-fj7xt1/1 Running 3 2d10.42.234.206 oom default beijing-aaf-sms-quorumclient-0 1/1 Running 0 2d10.42.252.144 oom default beijing-aaf-sms-quorumclient-1 1/1 Running 0 2d10.42.18.61 oom-1 default beijing-aaf-sms-quorumclient-2 1/1 Running 0 2d10.42.183.35oom-1 default beijing-aaf-sms-vault-0 2/2 Running 1 2d10.42.82.54 oom default beijing-aai-795958c985-92krm1/1 Running 3 2d10.42.90.176oom default beijing-aai-babel-555c485c8f-zlq65 2/2 Running 0 2d10.42.148.162 oom default beijing-aai-cassandra-0 0/1 Running 1 2d10.42.51.213oom default beijing-aai-cassandra-1 1/1 Running 0 2d10.42.114.132 oom-1 default beijing-aai-cassandra-2 1/1 Running 0 2d10.42.209.20oom-1 default beijing-aai-champ-79fff8f5b9-nj5pn 1/1 Running 0 2d10.42.18.51 oom default beijing-aai-data-router-9b86999fb-7f75h 1/1 Running 0 2d10.42.184.131 oom default beijing-aai-elasticsearch-56f6588bc6-kxjjg 1/1 Running 3 2d10.42.110.10oom default beijing-aai-gizmo-76c5bdb676-85cv4 2/2 Running 3 2d10.42.129.250 oom default beijing-aai-hbase-6b95d5df68-zqgbs 1/1 Running 0 2d10.42.173.156 oom default beijing-aai-modelloader-bbfcf8d47-8frl7 2/2 Running 0 2d10.42.62.160oom default beijing-aai-resources-6d789d65d7-nrcmj 2/2 Running 0 2d10.42.207.22oom default beijing-aai-search-data-75bd845479-zjpvj2/2 Running 2 2d10.42.83.89 oom default beijing-aai-sparky-be-7f786b5445-hw4z6 2/2 Running 2 2d10.42.181.219 oom default beijing-aai-traversal-699575dc59-zcmq7 2/2 Running 0 2d10.42.191.223 oom default beijing-aai-traversal-update-query-data-55cmk 0/1 Init:0/13 2d10.42.126.230 oom default beij
Re: [onap-discuss] Issues pulling images from docker.io through our Nexus3 proxy.
Hi Jess, I deployed now and it works like a charm. Thanks a lot! Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On Behalf Of Jessica Wagantall Sent: Thursday, June 28, 2018 1:22 AM To: onap-discuss@lists.onap.org; onap-release ; Kenny Paul Subject: Re: [onap-discuss] Issues pulling images from docker.io through our Nexus3 proxy. Team, Can we please give it a shot now again to your images? From my tests 5 out of 5 pulls succeeded. Not like before when I had to re-try up to 3 times. I will go through the RTs and tackle them individually. Please expect my reply on them. Thanks! Jess On Wed, Jun 27, 2018 at 2:59 PM, Jessica Wagantall mailto:jwagant...@linuxfoundation.org>> wrote: Dear team, I wanted to let you know that I am still investigating these issues. In my case (in my local machine) running the same pull requests sometimes succeeds and sometimes it fails to find the proper manifest. Nothing in our environment has changed, but I am looking through the logs to see if I can catch something happening. Sorry for the inconvenience, I'll continue working on this. Thanks! Jess 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 <https://www.amdocs.com/about/email-disclaimer> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10657): https://lists.onap.org/g/onap-discuss/message/10657 Mute This Topic: https://lists.onap.org/mt/22785369/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [ONAP Helpdesk #57746] RE: [onap-discuss] nexus3.onap.org stopped proxy of docker.io images
This was for few days, for several images.
Looks like proxy mode was / is not working.
Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726
From: Jessica Wagantall via RT
Sent: Wednesday, June 27, 2018 19:55
To: Borislav Glozman
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #57746] RE: [onap-discuss] nexus3.onap.org stopped
proxy of docker.io images
This seemed to have happened for other teams as well.
I have just ran the command and was able to download it:
docker pull nexus3.onap.org:10001/library/cassandra:3.11
3.11: Pulling from library/cassandra
f2aa67a397c4: Already exists
7883c8e950c9: Pull complete
17fef4315177: Pull complete
de8642533b1e: Pull complete
fc91ae190319: Pull complete
c8de95d40c25: Pull complete
d66bea82a2da: Pull complete
6e85c3794992: Pull complete
7e67c1874abb: Pull complete
901a929c2fa8: Pull complete
Digest: sha256:7155cb41dd1a508c5ea67b1750e98381d495873637aea6dcb9a5b13e3b2fb133
Status: Downloaded newer image for nexus3.onap.org:10001/library/cassandra:3.11
Can you please try again? I am wondering if this was a small glitch issue.
Thanks!
Jess
On Wed Jun 27 10:10:46 2018, borislav.gloz...@amdocs.com wrote:
> Resending with helpdesk.
>
> Thanks,
> Borislav Glozman
> O:+972.9.776.1988
> M:+972.52.2835726
> [amdocs-a]
> Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-
> network/nfv-powered-by-onap>
>
> From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org]
> On Behalf Of Borislav Glozman
> Sent: Tuesday, June 26, 2018 6:11 PM
> To: onap-discuss@lists.onap.org
> Cc: Jessica Wagantall
> Subject: [onap-discuss] nexus3.onap.org stopped proxy of docker.io
> images
>
> Hi,
>
> I noticed when deploying ONAP deployment on K8S that images that come
> from docker.io are not downloaded via nexus3.onap.org
> For example: nexus3.onap.org:10001/ library/cassandra:3.11
> I am getting error from nexus3:
> https://nexus3.onap.org/repository/docker.io/v2/library/cassandra/manifests/3.11
> {"errors":[{"code":"UNAUTHORIZED","message":"authentication
> required","detail":[{"Type":"repository","Class":"","Name":"library/cassandra","Action":"pull"}]}]}
>
> Path
>
> v2/library/cassandra/manifests/3.11<https://nexus3.onap.org/repository/docker.io/v2/library/cassandra/manifests/3.11>
>
> Content type
>
> application/vnd.docker.distribution.manifest.v2+json
>
> File size
>
> 2.4 KB
>
> Blob created
>
> Wed Apr 25 2018 09:35:44 GMT+0300 (Israel Daylight Time)
>
> Blob updated
>
> Mon Apr 30 2018 13:27:29 GMT+0300 (Israel Daylight Time)
>
> Last 30 days
>
> 0 downloads
>
> Last downloaded
>
> Tue Jun 26 2018 18:05:21 GMT+0300 (Israel Daylight Time)
>
> Locally cached
>
> true
>
> Blob reference
>
> default@BE552485-1ACD19AD-4F5AA0F6-50E80C8B-4ADDA1F1:e52b1b31-05f6-
> 4d93-bff9-0219fb055389
>
> Containing repo
>
> docker.io
>
> Uploader
>
> docker
>
> Uploader's IP Address
>
> 66.46.199.130
>
>
> Could you please fix this?
>
> Thanks,
> Borislav Glozman
> O:+972.9.776.1988
> M:+972.52.2835726
> [amdocs-a]
> Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-
> network/nfv-powered-by-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
>
> 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
> <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
<https://www.amdocs.com/about/email-disclaimer>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10633): https://lists.onap.org/g/onap-discuss/message/10633
Mute This Topic: https://lists.onap.org/mt/22734364/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [NEWSLETTER] [onap-discuss] k8s sandbox changed message
In onap/values.yaml file under relevant component you can add "repository" parameter with the values you would like to use, similar to how it is defined in the chart values.yaml file. I think the problem is in nexus3.onap.org. I already sent an email to LF helpdesk. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: Vidhu Shekhar Pandey - ERS, HCL Tech [mailto:vidhu.pan...@hcl.com] Sent: Wednesday, June 27, 2018 7:19 PM To: Borislav Glozman ; onap-discuss@lists.onap.org Subject: RE: [NEWSLETTER] [onap-discuss] k8s sandbox changed message Hi Borislav, I did not get what to change in onap/values.yaml to override. Could you please let me know? After several attempts the pod finally was able to pull the image without any changes but facing similar problem with other pods too like nexus, policydb, portal-zookeeper etc. Thanks, Vidhu From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com] Sent: 27 June 2018 11:50 To: Vidhu Shekhar Pandey - ERS, HCL Tech mailto:vidhu.pan...@hcl.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: RE: [NEWSLETTER] [onap-discuss] k8s sandbox changed message Hi, I encountered this problem yesterday and sent an email (attached). Seems like nexus3.onap.org stopped proxying docker.io images. You can override those image registry params using onap/values.yaml file as a workaround for now. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.amdocs.com%2Fopen-network%2Fnfv-powered-by-onap=02%7C01%7Cvidhu.pandey%40hcl.com%7C7f5aa10d63cb44ef0f1808d5dbf618ee%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636656772396293018=luP9vyL7b13RyCV1V%2B6GuPufNI0Oh2INMujZeElwwaA%3D=0> From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> [mailto:onap-discuss@lists.onap.org] On Behalf Of Vidhu Shekhar Pandey - ERS, HCL Tech Sent: Tuesday, June 26, 2018 8:10 PM To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: [NEWSLETTER] [onap-discuss] k8s sandbox changed message Unsubscribe It appears that you have subscribed to commercial messages from this sender. To stop receiving such messages from this sender, please unsubscribe<https://apac01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsecure-web.cisco.com%2F1MOgfWBDrn-wHQNtzm_Ey6eiKzdHJlcCcWkjp0LpmR3R2zyGUHrQsaBKtjKdvparqh78hryNwv9WaY3tJoQiAz0l25YMHj-pAa5lJGSrEllCWEj1RDCPMIG_-bjlfRNjVblwQ5-lIFJB50qImaFptPKrFcQlf_sxxzydrOjsc56sqPVVKL3DNnMa07ofU5tIk0VStszhLDm0Hv83kwZr-XL_cgSac9DFo6U3qrJHvmEtgEwTMnZfOIfoYj_AH-52rzgN0JFkosmVe1PZ420wj9F-K0FTkR-u7bqLOGpTpAePGqqWekgQIQx0q1rAkkbncxTtYLj5BubnfYnH4X0gEj2DuQzJh5EYWPAoHZ8U6RscdBVaN_4G-02dNYro6MLC2juGy4NGb7o_-UpKehB2i37BL2cmknKTooCg1vNVuJ1kz4YW_plMgm7t4fPbZN9FJ%2Fl43%253Ahttps%253A%252F%252Flists.onap.org%252Fg%252Fonap-discuss%252Funsube=02%7C01%7Cvidhu.pandey%40hcl.com%7C7f5aa10d63cb44ef0f1808d5dbf618ee%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636656772396303031=u%2FIXsRoO7lfqavlxlVosGybz3FROMOG15qdoJFzR9ng%3D=0> Hi, Has anyone encountered the "Pod sandbox changed" message in pod description? I get following problem with some of the pods if when I re-run the pods on a k8s 4 node cluster with Rancher for OOM Beijing setup Normal SandboxChanged 24mkubelet, k8s-beijing-2 Pod sandbox changed, it will be killed and re-created. Normal Pulling16m (x4 over 26m) kubelet, k8s-beijing-2 pulling image "nexus3.onap.org:10001/library/consul:1.0.6<https://apac01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fnexus3.onap.org%3A10001%2Flibrary%2Fconsul%3A1.0.6=02%7C01%7Cvidhu.pandey%40hcl.com%7Cdda9e91bd5974817328708d5db72573c%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636656206533194097=c1DPffV57O%2BkqnRHq2ujrdWXr7weCNKr9vpNKvWvDUM%3D=0>" Warning Failed 16m (x4 over 26m) kubelet, k8s-beijing-2 Failed to pull image "nexus3.onap.org:10001/library/vault:0.10.0<https://apac01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fnexus3.onap.org%3A10001%2Flibrary%2Fvault%3A0.10.0=02%7C01%7Cvidhu.pandey%40hcl.com%7Cdda9e91bd5974817328708d5db72573c%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636656206533204118=ZCJnGslvlN2Kz8rgIKf835Z480NwbRo1g9Lc%2BQa%2FWsw%3D=0>": rpc error: code = Canceled desc = context canceled Warning FailedSync 14m (x4 over 24m) kubelet, k8s-beijing-2 Error syncing pod Normal Pulling14m (x5 over 27m) kubelet, k8s-beijing-2 pulling image "nexus3.onap.org:10001/library/vault:0.10.0<https://apac01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fnexus3.onap.org%3A10001%2Flibrary%2Fvault%3A0.10.0=02%7C01%7Cvidhu.pandey%40hcl.
Re: [onap-discuss] nexus3.onap.org stopped proxy of docker.io images
Resending with helpdesk.
Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726
[amdocs-a]
Amdocs a Platinum member of
ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap>
From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On
Behalf Of Borislav Glozman
Sent: Tuesday, June 26, 2018 6:11 PM
To: onap-discuss@lists.onap.org
Cc: Jessica Wagantall
Subject: [onap-discuss] nexus3.onap.org stopped proxy of docker.io images
Hi,
I noticed when deploying ONAP deployment on K8S that images that come from
docker.io are not downloaded via nexus3.onap.org
For example: nexus3.onap.org:10001/ library/cassandra:3.11
I am getting error from nexus3:
https://nexus3.onap.org/repository/docker.io/v2/library/cassandra/manifests/3.11
{"errors":[{"code":"UNAUTHORIZED","message":"authentication
required","detail":[{"Type":"repository","Class":"","Name":"library/cassandra","Action":"pull"}]}]}
Path
v2/library/cassandra/manifests/3.11<https://nexus3.onap.org/repository/docker.io/v2/library/cassandra/manifests/3.11>
Content type
application/vnd.docker.distribution.manifest.v2+json
File size
2.4 KB
Blob created
Wed Apr 25 2018 09:35:44 GMT+0300 (Israel Daylight Time)
Blob updated
Mon Apr 30 2018 13:27:29 GMT+0300 (Israel Daylight Time)
Last 30 days
0 downloads
Last downloaded
Tue Jun 26 2018 18:05:21 GMT+0300 (Israel Daylight Time)
Locally cached
true
Blob reference
default@BE552485-1ACD19AD-4F5AA0F6-50E80C8B-4ADDA1F1:e52b1b31-05f6-4d93-bff9-0219fb055389
Containing repo
docker.io
Uploader
docker
Uploader's IP Address
66.46.199.130
Could you please fix this?
Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726
[amdocs-a]
Amdocs a Platinum member of
ONAP<https://www.amdocs.com/open-network/nfv-powered-by-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
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
<https://www.amdocs.com/about/email-disclaimer>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10622): https://lists.onap.org/g/onap-discuss/message/10622
Mute This Topic: https://lists.onap.org/mt/22685369/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [NEWSLETTER] [onap-discuss] k8s sandbox changed message
Hi, I encountered this problem yesterday and sent an email (attached). Seems like nexus3.onap.org stopped proxying docker.io images. You can override those image registry params using onap/values.yaml file as a workaround for now. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On Behalf Of Vidhu Shekhar Pandey - ERS, HCL Tech Sent: Tuesday, June 26, 2018 8:10 PM To: onap-discuss@lists.onap.org Subject: [NEWSLETTER] [onap-discuss] k8s sandbox changed message Unsubscribe It appears that you have subscribed to commercial messages from this sender. To stop receiving such messages from this sender, please unsubscribe<http://secure-web.cisco.com/1MOgfWBDrn-wHQNtzm_Ey6eiKzdHJlcCcWkjp0LpmR3R2zyGUHrQsaBKtjKdvparqh78hryNwv9WaY3tJoQiAz0l25YMHj-pAa5lJGSrEllCWEj1RDCPMIG_-bjlfRNjVblwQ5-lIFJB50qImaFptPKrFcQlf_sxxzydrOjsc56sqPVVKL3DNnMa07ofU5tIk0VStszhLDm0Hv83kwZr-XL_cgSac9DFo6U3qrJHvmEtgEwTMnZfOIfoYj_AH-52rzgN0JFkosmVe1PZ420wj9F-K0FTkR-u7bqLOGpTpAePGqqWekgQIQx0q1rAkkbncxTtYLj5BubnfYnH4X0gEj2DuQzJh5EYWPAoHZ8U6RscdBVaN_4G-02dNYro6MLC2juGy4NGb7o_-UpKehB2i37BL2cmknKTooCg1vNVuJ1kz4YW_plMgm7t4fPbZN9FJ/l43%3Ahttps%3A%2F%2Flists.onap.org%2Fg%2Fonap-discuss%2Funsube> Hi, Has anyone encountered the "Pod sandbox changed" message in pod description? I get following problem with some of the pods if when I re-run the pods on a k8s 4 node cluster with Rancher for OOM Beijing setup Normal SandboxChanged 24mkubelet, k8s-beijing-2 Pod sandbox changed, it will be killed and re-created. Normal Pulling16m (x4 over 26m) kubelet, k8s-beijing-2 pulling image "nexus3.onap.org:10001/library/consul:1.0.6<https://apac01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fnexus3.onap.org%3A10001%2Flibrary%2Fconsul%3A1.0.6=02%7C01%7Cvidhu.pandey%40hcl.com%7Cdda9e91bd5974817328708d5db72573c%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636656206533194097=c1DPffV57O%2BkqnRHq2ujrdWXr7weCNKr9vpNKvWvDUM%3D=0>" Warning Failed 16m (x4 over 26m) kubelet, k8s-beijing-2 Failed to pull image "nexus3.onap.org:10001/library/vault:0.10.0<https://apac01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fnexus3.onap.org%3A10001%2Flibrary%2Fvault%3A0.10.0=02%7C01%7Cvidhu.pandey%40hcl.com%7Cdda9e91bd5974817328708d5db72573c%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636656206533204118=ZCJnGslvlN2Kz8rgIKf835Z480NwbRo1g9Lc%2BQa%2FWsw%3D=0>": rpc error: code = Canceled desc = context canceled Warning FailedSync 14m (x4 over 24m) kubelet, k8s-beijing-2 Error syncing pod Normal Pulling14m (x5 over 27m) kubelet, k8s-beijing-2 pulling image "nexus3.onap.org:10001/library/vault:0.10.0<https://apac01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fnexus3.onap.org%3A10001%2Flibrary%2Fvault%3A0.10.0=02%7C01%7Cvidhu.pandey%40hcl.com%7Cdda9e91bd5974817328708d5db72573c%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636656206533204118=ZCJnGslvlN2Kz8rgIKf835Z480NwbRo1g9Lc%2BQa%2FWsw%3D=0>" Warning Failed 11mkubelet, k8s-beijing-2 Failed to pull image "nexus3.onap.org:10001/library/consul:1.0.6<https://apac01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fnexus3.onap.org%3A10001%2Flibrary%2Fconsul%3A1.0.6=02%7C01%7Cvidhu.pandey%40hcl.com%7Cdda9e91bd5974817328708d5db72573c%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636656206533214122=tiSGtUUkR4IhB5Y2GIcKHvoFTduO335CvM%2FWXUGVNtI%3D=0>": rpc error: code = Unknown desc = Tag 1.0.6 not found The pod gets into a loop not able to pull the image. Can anyone explain the cause and way to fix this? Thanks, Vidhu ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized represen
[onap-discuss] nexus3.onap.org stopped proxy of docker.io images
Hi,
I noticed when deploying ONAP deployment on K8S that images that come from
docker.io are not downloaded via nexus3.onap.org
For example: nexus3.onap.org:10001/ library/cassandra:3.11
I am getting error from nexus3:
https://nexus3.onap.org/repository/docker.io/v2/library/cassandra/manifests/3.11
{"errors":[{"code":"UNAUTHORIZED","message":"authentication
required","detail":[{"Type":"repository","Class":"","Name":"library/cassandra","Action":"pull"}]}]}
Path
v2/library/cassandra/manifests/3.11<https://nexus3.onap.org/repository/docker.io/v2/library/cassandra/manifests/3.11>
Content type
application/vnd.docker.distribution.manifest.v2+json
File size
2.4 KB
Blob created
Wed Apr 25 2018 09:35:44 GMT+0300 (Israel Daylight Time)
Blob updated
Mon Apr 30 2018 13:27:29 GMT+0300 (Israel Daylight Time)
Last 30 days
0 downloads
Last downloaded
Tue Jun 26 2018 18:05:21 GMT+0300 (Israel Daylight Time)
Locally cached
true
Blob reference
default@BE552485-1ACD19AD-4F5AA0F6-50E80C8B-4ADDA1F1:e52b1b31-05f6-4d93-bff9-0219fb055389
Containing repo
docker.io
Uploader
docker
Uploader's IP Address
66.46.199.130
Could you please fix this?
Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726
[amdocs-a]
Amdocs a Platinum member of
ONAP<https://www.amdocs.com/open-network/nfv-powered-by-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
<https://www.amdocs.com/about/email-disclaimer>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10589): https://lists.onap.org/g/onap-discuss/message/10589
Mute This Topic: https://lists.onap.org/mt/22685369/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] [OOM] "serializer for text/html doesn't exist" error on helm insatll
Hi, Looks like there is either k8s deployment problem or helm version mismatch. More details would help... Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On Behalf Of subhash kumar singh Sent: Tuesday, June 26, 2018 5:06 PM To: onap-discuss@lists.onap.org Cc: Seshu m ; Praveen Krishnamurthy P Subject: [onap-discuss] [OOM] "serializer for text/html doesn't exist" error on helm insatll Hello Everyone, I am following wiki[1][2] to bring up the ONAP using OOM. But I am facing following issue on `helm install`: $ helm search -l | grep onap local/onap 2.0.0beijing Open Network Automation Platform (ONAP) $ helm install local/onap -n dev --namespace onap Error: serializer for text/html doesn't exist Please let me know how can I fix this issue. [1] http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_quickstart_guide.html#quick-start-label [2] http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_setup_kubernetes_rancher.html -- Regards, Subhash Kumar Singh FNOSS, ONAP Huawei Technologies India Pvt. Ltd. Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield Bengaluru-560066, Karnataka Tel: Mob: 8050101106 Email: subhash.kumar.si...@huawei.com<mailto:subhash.kumar.si...@huawei.com> [Company_logo] This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! 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 <https://www.amdocs.com/about/email-disclaimer> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10586): https://lists.onap.org/g/onap-discuss/message/10586 Mute This Topic: https://lists.onap.org/mt/22684845/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] policy-nexus in CrashLoopBackOff
Hi Santiago, Nexus liveliness timeout is too short, it doesn’t manage to start during it. I am opening a defect in OOM to increase the timeout: OOM-1139<https://jira.onap.org/browse/OOM-1139> - Policy Nexus liveness initialDelaySeconds is too short Meanwhile you can change policy/charts/drools/charts/nexus/values.yaml Increase both initialDelaySeconds to 180 and redeploy policy. Do not forget to do “make all”… Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Santi Rodríguez Sent: Wednesday, June 13, 2018 12:02 PM To: onap-discuss@lists.onap.org Subject: [onap-discuss] policy-nexus in CrashLoopBackOff Hi all, The policy component always worked fine for me but now the policy-nexus pod is in CrashLoopBackOff state. With the "kubectl describe pod" command I can see the next info: Warning Unhealthy 5m (x5 over 6m) kubelet, chubunteado Liveness probe failed: dial tcp 10.42.179.225:8081<http://10.42.179.225:8081>: getsockopt: connection refused Normal Pulled 5m (x3 over 7m) kubelet, chubunteado Container image "nexus3.onap.org:10001/sonatype/nexus:2.14.8-01<http://nexus3.onap.org:10001/sonatype/nexus:2.14.8-01>" already present on machine Normal Killing5m (x2 over 6m) kubelet, chubunteado Killing container with id docker://nexus:Container failed liveness probe.. Container will be killed and recreated. The log: - Initializing Nexus Repository Manager OSS 2.14.8-01 - 2018-06-13 08:52:57,070+ INFO [jetty-main-1] org.sonatype.nexus.NxApplication - Activating locally installed plugins... 2018-06-13 08:52:58,457+ INFO [jetty-main-1] com.sun.jersey.server.impl.application.WebApplicationImpl - Initiating Jersey application, version 'Jersey: 1.17.1 02/28/2013 12:47 PM' 2018-06-13 08:53:01,341+ INFO [jetty-main-1] org.sonatype.nexus.plugins.bcprov.CryptoPlugin - Unlimited strength JCE policy detected 2018-06-13 08:53:02,312+ INFO [jetty-main-1] org.sonatype.nexus.kazuki.KazukiPlugin - Kazuki version: 0.1.8 2018-06-13 08:53:10,753+ INFO [jetty-main-1] org.sonatype.nexus.proxy.registry.DefaultRepositoryTypeRegistry - Registered Repository type RepositoryType=(org.sonatype.nexus.proxy.repository.ShadowRepository:nuget-shadow). 2018-06-13 08:53:10,759+ INFO [jetty-main-1] org.sonatype.nexus.proxy.registry.DefaultRepositoryTypeRegistry - Registered Repository type RepositoryType=(org.sonatype.nexus.proxy.repository.GroupRepository:nuget-group). 2018-06-13 08:53:10,759+ INFO [jetty-main-1] org.sonatype.nexus.proxy.registry.DefaultRepositoryTypeRegistry - Registered Repository type RepositoryType=(org.sonatype.nexus.proxy.repository.Repository:nuget-proxy). 2018-06-13 08:53:11,015+ INFO [jetty-main-1] org.sonatype.nexus.proxy.registry.DefaultRepositoryTypeRegistry - Registered Repository type RepositoryType=(org.sonatype.nexus.proxy.repository.GroupRepository:npm-group). 2018-06-13 08:53:11,016+ INFO [jetty-main-1] org.sonatype.nexus.proxy.registry.DefaultRepositoryTypeRegistry - Registered Repository type RepositoryType=(org.sonatype.nexus.proxy.repository.Repository:npm-proxy). 2018-06-13 08:53:11,016+ INFO [jetty-main-1] org.sonatype.nexus.proxy.registry.DefaultRepositoryTypeRegistry - Registered Repository type RepositoryType=(org.sonatype.nexus.proxy.repository.Repository:npm-hosted). 2018-06-13 08:53:12,796+ INFO [jetty-main-1] org.sonatype.nexus.proxy.registry.DefaultRepositoryTypeRegistry - Registered Repository type RepositoryType=(org.sonatype.nexus.proxy.repository.GroupRepository:rubygems-group). 2018-06-13 08:53:12,802+ INFO [jetty-main-1] org.sonatype.nexus.proxy.registry.DefaultRepositoryTypeRegistry - Registered Repository type RepositoryType=(org.sonatype.nexus.proxy.repository.Repository:rubygems-proxy). 2018-06-13 08:53:12,802+ INFO [jetty-main-1] org.sonatype.nexus.proxy.registry.DefaultRepositoryTypeRegistry - Registered Repository type RepositoryType=(org.sonatype.nexus.proxy.repository.Repository:rubygems-hosted). 2018-06-13 08:53:16,266+ INFO [jetty-main-1] org.sonatype.nexus.proxy.registry.DefaultRepositoryTypeRegistry - Registered Repository type RepositoryType=(org.sonatype.nexus.proxy.repository.WebSiteRepository:site). 2018-06-13 08:53:17,984+ INFO [jetty-main-1] org.sonatype.nexus.NxApplication - Plugin manager request "ACTIVATE" on plugin "org.sonatype.nexus.plugins:nexus-rutauth-plugin:2.14.8-01" was successful. 2018-06-13 08:53:17,986+ INFO [jetty-main-1] org.sonatype.nexus.NxApplication - Plugin manager request &
Re: [onap-discuss] Install ONAP Beijing Release
Hi Paul, Looks like you are following old instructions. You probably have one node and there is a limitation of 110 pods per node. Please follow the instructions that Roger suggested in his email (attached) Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: Soumyarup Paul [mailto:soumyarup.p...@infosys.com] Sent: Thursday, June 7, 2018 6:07 PM To: Borislav Glozman ; Roger Maitland ; 'onap-discuss@lists.onap.org' Cc: Syed Atif Husain ; Gopal Sabhadiya Subject: RE: Install ONAP Beijing Release Hi Borislav, Thanks for the suggestion. My helm repo got fixed and I was able to install ONAP but 30 pods are not running. I am using the cd.sh script written by Michael O’Brien and following the ONAP on Kubernetes installation flow. Can you please suggest something for this? PFA – List of non-running pods Thanks and Regards, Soumyarup Paul From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com] Sent: Wednesday, June 6, 2018 8:34 PM To: Soumyarup Paul mailto:soumyarup.p...@infosys.com>>; 'onap-discuss@lists.onap.org' mailto:onap-discuss@lists.onap.org>> Cc: Syed Atif Husain mailto:syed...@infosys.com>>; Gopal Sabhadiya mailto:gopal.sabhad...@infosys.com>> Subject: RE: Install ONAP Beijing Release Looks like something happened to helm repo and it is not running on your host. Please run ‘nohup helm serve &’ and retry. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.amdocs.com%2Fopen-network%2Fnfv-powered-by-onap=01%7C01%7Csoumyarup.paul%40infosys.com%7C08336baabed2470290e908d5cbbee5b4%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1=TOIlyRpaOK25wwUuPQDLCl3DrlXcbbAr%2FKCwCpSI1AM%3D=0> From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Soumyarup Paul Sent: Wednesday, June 6, 2018 1:47 PM To: 'onap-discuss@lists.onap.org' mailto:onap-discuss@lists.onap.org>> Cc: Syed Atif Husain mailto:syed...@infosys.com>>; Gopal Sabhadiya mailto:gopal.sabhad...@infosys.com>> Subject: [onap-discuss] Install ONAP Beijing Release Hi All, I am facing a few issues while installing the Beijing release. 1. In the cd.sh script, should I uncomment this move file code if [ "$BRANCH" == "master" ]; then echo "moving values.yaml to oom/kubernetes/" #sudo cp values.yaml oom/kubernetes/onap If so, what is the encryption method used for password which I would need to provide here – openStackEncryptedPasswordHere: "c124921a3a0efbe579782cde8227681e" 2. If I try to install using the default values then I get the following error – List of ONAP Modules - look for terminating pods NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE kube-system heapster-76b8cd7b5-dl28v 1/1 Running 0 7d10.42.34.140 blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net kube-system kube-dns-5d7b4487c9-6d6m2 3/3 Running 0 7d10.42.207.251 blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net kube-system kubernetes-dashboard-f9577fffd-k5snh 1/1 Running 0 7d10.42.149.137 blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net kube-system monitoring-grafana-997796fcf-qdps2 1/1 Running 0 7d10.42.132.98 blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net kube-system monitoring-influxdb-56fdcd96b-xctvq1/1 Running 0 7d10.42.208.55 blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net kube-system tiller-deploy-54bcc55dd5-scrbq 1/1 Running 0 7d10.42.61.176 blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net deleting /dockerdata-nfs chmod: cannot access '/dockerdata-nfs/onap': No such file or directory chmod: cannot access '/dockerdata-nfs/dev': No such file or directory pull new oom Cloning into 'oom'... remote: Total 16470 (delta 0), reused 16470 (delta 0) Receiving objects: 100% (16470/16470), 24.04 MiB | 14.89 MiB/s, done. Resolving deltas: 100% (8252/8252), done. Checking connectivity... done. moving values.yaml to oom/kubernetes/ start onap pods [common] make[1]: Entering directory '/root/oom/kubernetes' make[2]: Entering directory '/root/oom/kubernetes/common' [common] make[3]: Entering directory '/root/oom/kubernetes/common' ==> Linting common [INFO] Chart.yaml: icon is recommended 1 chart(s) linted, no failures Successfully packaged chart and saved it
Re: [onap-discuss] Install ONAP Beijing Release
Looks like something happened to helm repo and it is not running on your host. Please run ‘nohup helm serve &’ and retry. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Soumyarup Paul Sent: Wednesday, June 6, 2018 1:47 PM To: 'onap-discuss@lists.onap.org' Cc: Syed Atif Husain ; Gopal Sabhadiya Subject: [onap-discuss] Install ONAP Beijing Release Hi All, I am facing a few issues while installing the Beijing release. 1. In the cd.sh script, should I uncomment this move file code if [ "$BRANCH" == "master" ]; then echo "moving values.yaml to oom/kubernetes/" #sudo cp values.yaml oom/kubernetes/onap If so, what is the encryption method used for password which I would need to provide here – openStackEncryptedPasswordHere: "c124921a3a0efbe579782cde8227681e" 2. If I try to install using the default values then I get the following error – List of ONAP Modules - look for terminating pods NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE kube-system heapster-76b8cd7b5-dl28v 1/1 Running 0 7d10.42.34.140 blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net kube-system kube-dns-5d7b4487c9-6d6m2 3/3 Running 0 7d10.42.207.251 blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net kube-system kubernetes-dashboard-f9577fffd-k5snh 1/1 Running 0 7d10.42.149.137 blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net kube-system monitoring-grafana-997796fcf-qdps2 1/1 Running 0 7d10.42.132.98 blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net kube-system monitoring-influxdb-56fdcd96b-xctvq1/1 Running 0 7d10.42.208.55 blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net kube-system tiller-deploy-54bcc55dd5-scrbq 1/1 Running 0 7d10.42.61.176 blade-onap2.rk0x55rzv0zubgwnjk20ayoq5f.bx.internal.cloudapp.net deleting /dockerdata-nfs chmod: cannot access '/dockerdata-nfs/onap': No such file or directory chmod: cannot access '/dockerdata-nfs/dev': No such file or directory pull new oom Cloning into 'oom'... remote: Total 16470 (delta 0), reused 16470 (delta 0) Receiving objects: 100% (16470/16470), 24.04 MiB | 14.89 MiB/s, done. Resolving deltas: 100% (8252/8252), done. Checking connectivity... done. moving values.yaml to oom/kubernetes/ start onap pods [common] make[1]: Entering directory '/root/oom/kubernetes' make[2]: Entering directory '/root/oom/kubernetes/common' [common] make[3]: Entering directory '/root/oom/kubernetes/common' ==> Linting common [INFO] Chart.yaml: icon is recommended 1 chart(s) linted, no failures Successfully packaged chart and saved it to: /root/oom/kubernetes/dist/packages/common-2.0.0.tgz make[3]: Leaving directory '/root/oom/kubernetes/common' [mariadb-galera] make[3]: Entering directory '/root/oom/kubernetes/common' Hang tight while we grab the latest from your chart repositories... ...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879/charts): Get http://127.0.0.1:8879/charts/index.yaml: dial tcp 127.0.0.1:8879: getsockopt: connection refused ...Successfully got an update from the "stable" chart repository Update Complete. ⎈Happy Helming!⎈ Saving 1 charts Deleting outdated charts ==> Linting mariadb-galera [INFO] Chart.yaml: icon is recommended 1 chart(s) linted, no failures Successfully packaged chart and saved it to: /root/oom/kubernetes/dist/packages/mariadb-galera-2.0.0.tgz make[3]: Leaving directory '/root/oom/kubernetes/common' [mongo] make[3]: Entering directory '/root/oom/kubernetes/common' Hang tight while we grab the latest from your chart repositories... ...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879/charts): Get http://127.0.0.1:8879/charts/index.yaml: dial tcp 127.0.0.1:8879: getsockopt: connection refused ...Successfully got an update from the "stable" chart repository Update Complete. ⎈Happy Helming!⎈ Saving 1 charts Downloading common from repo http://127.0.0.1:8879/charts Save error occurred: could not download http://127.0.0.1:8879/charts/common-2.0.0.tgz: Get http://127.0.0.1:8879/charts/common-2.0.0.tgz: dial tcp 127.0.0.1:8879: getsockopt: connection refused Deleting newly downloaded charts, restoring pre-update state Error: could not download http://127.0.0.1:8879/charts/common-2.0
Re: [onap-discuss] A service naming in OOM
Created bug: OOM-1102<https://jira.onap.org/browse/OOM-1102> Raised Gerrit review: 48477<https://gerrit.onap.org/r/#/c/48477/> Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Borislav Glozman Sent: Tuesday, May 22, 2018 11:40 AM To: C.T. Paterson <ctpaterson+o...@gmail.com>; Susan Bylsma <susan.byl...@amdocs.com> Cc: KAJUR, HARISH V <vk2...@att.com>; onap-discuss@lists.onap.org; James MacNider <james.macni...@amdocs.com> Subject: Re: [onap-discuss] A service naming in OOM Hi, The service is actually aai and not “aai-aai”. There are some places that specify “aai-aai”, causing inconsistency, they have to be fixed. Opening a bug on this. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of C.T. Paterson Sent: Saturday, May 19, 2018 2:53 PM To: Susan Bylsma <susan.byl...@amdocs.com<mailto:susan.byl...@amdocs.com>> Cc: KAJUR, HARISH V <vk2...@att.com<mailto:vk2...@att.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; James MacNider <james.macni...@amdocs.com<mailto:james.macni...@amdocs.com>> Subject: Re: [onap-discuss] A service naming in OOM I stand corrected. Thanks, Susan. Cheers. On 18 May 2018 at 02:34, Susan Bylsma <susan.byl...@amdocs.com<mailto:susan.byl...@amdocs.com>> wrote: Hi James and CT, “aai-aai” actually refers to the HA Proxy service. Microservices/components that need to contact the A APIs do so via the HA proxy service which is why you will see references to “aai-aai” in the Helm charts. Hope that helps, Susan On May 16, 2018, at 3:48 AM, C.T. Paterson <ctpaterson+o...@gmail.com<mailto:ctpaterson+o...@gmail.com>> wrote: Hi James, Not sure if you and Harish talked offline, but just noticed this note. I believe the AAI service should be considered retired. It predates the Amsterdam release when it was decomposed into the Resources and Traversal microservice which collectively supplanted its functionality. Cheers. On 4 May 2018 at 13:48, James MacNider <james.macni...@amdocs.com<mailto:james.macni...@amdocs.com>> wrote: Hi Harish, I’ve got a question about the naming of the A 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 is a Platinuim Member of ONAP<https://onap.org/> 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<mailto:onap-discuss@lists.onap.org&
Re: [onap-discuss] A service naming in OOM
Hi, The service is actually aai and not “aai-aai”. There are some places that specify “aai-aai”, causing inconsistency, they have to be fixed. Opening a bug on this. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of C.T. Paterson Sent: Saturday, May 19, 2018 2:53 PM To: Susan Bylsma <susan.byl...@amdocs.com> Cc: KAJUR, HARISH V <vk2...@att.com>; onap-discuss@lists.onap.org; James MacNider <james.macni...@amdocs.com> Subject: Re: [onap-discuss] A service naming in OOM I stand corrected. Thanks, Susan. Cheers. On 18 May 2018 at 02:34, Susan Bylsma <susan.byl...@amdocs.com<mailto:susan.byl...@amdocs.com>> wrote: Hi James and CT, “aai-aai” actually refers to the HA Proxy service. Microservices/components that need to contact the A APIs do so via the HA proxy service which is why you will see references to “aai-aai” in the Helm charts. Hope that helps, Susan On May 16, 2018, at 3:48 AM, C.T. Paterson <ctpaterson+o...@gmail.com<mailto:ctpaterson+o...@gmail.com>> wrote: Hi James, Not sure if you and Harish talked offline, but just noticed this note. I believe the AAI service should be considered retired. It predates the Amsterdam release when it was decomposed into the Resources and Traversal microservice which collectively supplanted its functionality. Cheers. On 4 May 2018 at 13:48, James MacNider <james.macni...@amdocs.com<mailto:james.macni...@amdocs.com>> wrote: Hi Harish, I’ve got a question about the naming of the A 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 is a Platinuim Member of ONAP<https://onap.org/> 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<mailto:onap-discuss@lists.onap.org> https://lists.onap.org/mailman/listinfo/onap-discuss ___ onap-discuss mailing list onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> https://lists.onap.org/mailman/listinfo/onap-discuss 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 <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] [oom] [aai] Resources fails to start
-cassandra-2 1/1 Running 0 19m 10.244.1.14 kubernetes-node5-borislavto-13099-05-13-18.novalocal onap aaa-aai-champ-77f7468b45-xj4vh 0/1 Running 0 20m 10.244.4.13 kubernetes-node1-borislavto-13099-05-13-18.novalocal onap aaa-aai-data-router-7989ff6fff-99c92 1/1 Running 0 20m 10.244.3.13 kubernetes-node2-borislavto-13099-05-13-18.novalocal onap aaa-aai-elasticsearch-5f7447dcb9-mndvt 1/1 Running 0 20m 10.244.5.16 kubernetes-node3-borislavto-13099-05-13-18.novalocal onap aaa-aai-gizmo-9b5887fc7-g7tgq 2/2 Running 0 20m 10.244.7.13 kubernetes-node7-borislavto-13099-05-13-18.novalocal onap aaa-aai-hbase-6fd66cc9f4-ldjcs 1/1 Running 0 20m 10.244.4.14 kubernetes-node1-borislavto-13099-05-13-18.novalocal onap aaa-aai-modelloader-69cbcf4cfd-8mrsz 2/2 Running 0 20m 10.244.2.15 kubernetes-node4-borislavto-13099-05-13-18.novalocal onap aaa-aai-resources-6f7c69cf75-vnsrh 2/2 Running 0 20m 10.244.2.16 kubernetes-node4-borislavto-13099-05-13-18.novalocal onap aaa-aai-search-data-5df78c666f-scmvq 2/2 Running 0 20m 10.244.1.13 kubernetes-node5-borislavto-13099-05-13-18.novalocal onap aaa-aai-sparky-be-6f7cb4858-skmnh 2/2 Running 0 20m 10.244.3.14 kubernetes-node2-borislavto-13099-05-13-18.novalocal onap aaa-aai-traversal-f9b85cf97-gv7dn 2/2 Running 0 20m 10.244.4.15 kubernetes-node1-borislavto-13099-05-13-18.novalocal onap aaa-aai-traversal-update-query-data-lnxt8 0/1 Completed 0 20m 10.244.5.17 kubernetes-node3-borislavto-13099-05-13-18.novalocal onap aaa-dbc-pg-0 1/1 Running 0 14m 10.244.6.20 kubernetes-node6-borislavto-13099-05-13-18.novalocal onap aaa-dbc-pg-1 1/1 Running 0 13m 10.244.4.17 kubernetes-node1-borislavto-13099-05-13-18.novalocal onap aaa-dmaap-bus-controller-8545ffdfb7-4g2f9 1/1 Running 0 14m 10.244.5.18 kubernetes-node3-borislavto-13099-05-13-18.novalocal onap aaa-message-router-57ddbd6ff7-wd6zb 1/1 Running 0 14m 10.244.7.14 kubernetes-node7-borislavto-13099-05-13-18.novalocal onap aaa-message-router-kafka-7dfddbcdbb-cl8mv 1/1 Running 0 14m 10.244.4.16 kubernetes-node1-borislavto-13099-05-13-18.novalocal onap aaa-message-router-zookeeper-598c6c6996-mq2gn 1/1 Running 0 14m 10.244.3.16 kubernetes-node2-borislavto-13099-05-13-18.novalocal Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: HU, JUN NICOLAS [mailto:jh2...@att.com] Sent: Friday, May 11, 2018 6:27 PM To: Roger Maitland <roger.maitl...@amdocs.com>; Borislav Glozman <borislav.gloz...@amdocs.com>; Daniel Silverthorn <daniel.silverth...@amdocs.com>; onap-discuss@lists.onap.org; Steven Blimkie <steven.blim...@amdocs.com>; FORSYTH, JAMES <jf2...@att.com>; Mandeep Khinda <mandeep.khi...@amdocs.com> Subject: RE: [onap-discuss] [oom] [aai] Resources fails to start Hi Roger, Pulled latest OOM code this morning. I still got same error in kubeadm environment. The aai-resource try to connect to Cassandra via hostname. But got time out. Here is log from aai-resource container. Caused by: com.netflix.astyanax.connectionpool.exceptions.PoolTimeoutException: PoolTimeoutException: [host=onap-aai-cassandra-2(onap-aai-cassandra-2):9160, latency=30001(30001), attempts=3]Timed out waiting for connection So I checked the hostname, onap-aai-cassandra-1, realized that that hostname is unresolvable in kubeadm environment. aaiadmin@onap-aai-babel-8c6784976-96ph2:/$ ping onap-aai-cassandra-1 ping: unk
Re: [onap-discuss] [oom] [aai] Resources fails to start
Hi, Same problem here. Did anyone manage to resolve this? Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Daniel Silverthorn Sent: Monday, April 23, 2018 5:40 PM To: onap-discuss@lists.onap.org Subject: [onap-discuss] [oom] [aai] Resources fails to start Using the latest oom as of Friday, I am able to start aai on a single node k8s cluster, but when trying it on a multimode cluster, resources fails to start up with the following error: Exception in thread "main" java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48) at org.springframework.boot.loader.Launcher.launch(Launcher.java:87) at org.springframework.boot.loader.Launcher.launch(Launcher.java:50) at org.springframework.boot.loader.PropertiesLauncher.main(PropertiesLauncher.java:594) Caused by: java.lang.ExceptionInInitializerError at org.onap.aai.dbmap.AAIGraph.getInstance(AAIGraph.java:98) at org.onap.aai.dbgen.GenTester.main(GenTester.java:118) ... 8 more Caused by: java.lang.RuntimeException: Failed to instantiate graphs at org.onap.aai.dbmap.AAIGraph.(AAIGraph.java:83) at org.onap.aai.dbmap.AAIGraph.(AAIGraph.java:55) at org.onap.aai.dbmap.AAIGraph$Helper.(AAIGraph.java:88) ... 10 more Caused by: java.lang.IllegalArgumentException: Could not instantiate implementation: org.janusgraph.diskstorage.cassandra.astyanax.AstyanaxStoreManager at org.janusgraph.util.system.ConfigurationUtil.instantiate(ConfigurationUtil.java:69) at org.janusgraph.diskstorage.Backend.getImplementationClass(Backend.java:477) at org.janusgraph.diskstorage.Backend.getStorageManager(Backend.java:409) at org.janusgraph.graphdb.configuration.GraphDatabaseConfiguration.(GraphDatabaseConfiguration.java:1376) at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:164) at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:133) at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:113) at org.onap.aai.dbmap.AAIGraph.loadGraph(AAIGraph.java:110) at org.onap.aai.dbmap.AAIGraph.(AAIGraph.java:80) ... 12 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.janusgraph.util.system.ConfigurationUtil.instantiate(ConfigurationUtil.java:58) ... 20 more Caused by: org.janusgraph.diskstorage.TemporaryBackendException: Temporary failure in storage backend at org.janusgraph.diskstorage.cassandra.astyanax.AstyanaxStoreManager.ensureKeyspaceExists(AstyanaxStoreManager.java:619) at org.janusgraph.diskstorage.cassandra.astyanax.AstyanaxStoreManager.(AstyanaxStoreManager.java:314) ... 25 more Caused by: com.netflix.astyanax.connectionpool.exceptions.PoolTimeoutException: PoolTimeoutException: [host=aai-aai-cassandra-1(aai-aai-cassandra-1):9160, latency=30001(30001), attempts=3]Timed out waiting for connection at com.netflix.astyanax.connectionpool.impl.SimpleHostConnectionPool.waitForConnection(SimpleHostConnectionPool.java:231) at com.netflix.astyanax.connectionpool.impl.SimpleHostConnectionPool.borrowConnection(SimpleHostConnectionPool.java:198) at com.netflix.astyanax.connectionpool.impl.RoundRobinExecuteWithFailover.borrowConnection(RoundRobinExecuteWithFailover.java:84) at com.netflix.astyanax.connectionpool.impl.AbstractExecuteWithFailoverImpl.tryOperation(AbstractExecuteWithFailoverImpl.java:117) at com.netflix.astyanax.connectionpool.impl.AbstractHostPartitionConnectionPool.executeWithFailover(AbstractHostPartitionConnectionPool.java:352) at com.netflix.astyanax.thrift.ThriftClusterImpl.executeSchemaChangeOperation(ThriftClusterImpl.java:146) at com.netflix.astyanax.thrift.ThriftClusterImpl.internalCreateKeyspace(ThriftClusterImpl.java:321) at com.netflix.astyanax.thrift.ThriftClusterImpl.addKeyspace(ThriftClus
Re: [onap-discuss] [sdc] [oom] SDC Backend deployment errors
The problem stated below was solved in review:
https://gerrit.onap.org/r/#/c/43799/
Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726
[amdocs-a]
Amdocs a Platinum member of
ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap>
From: Satyaki Mallick [mailto:satyaki.commerci...@gmail.com]
Sent: Friday, April 20, 2018 8:24 AM
To: Lando,Michael <ml6...@intl.att.com>
Cc: Borislav Glozman <borislav.gloz...@amdocs.com>; Avinash S
<discoveravin...@gmail.com>
Subject: Re: [onap-discuss] [sdc] [oom] SDC Backend deployment errors
Hello,
Did anyone solve this issue?
We are also facing the same error...
Thank you,
Satyaki Mallick
On Mon, Apr 16, 2018 at 5:10 PM, Borislav Glozman
<borislav.gloz...@amdocs.com<mailto:borislav.gloz...@amdocs.com>> wrote:
Hello SDC experts,
I see deployment errors during SDC Backend deployment. Could you please assist
in resolving this?
Deployment descriptors can be found at:
https://gerrit.onap.org/r/gitweb?p=oom.git;a=tree;f=kubernetes/sdc/charts/sdc-be;h=e7c8981771080e301dce2b5d3faf3f08083ee38a;hb=refs/heads/master
Jetty starting log is attached.
Last Exception in the log:
2018-04-16 11:10:45.893:WARN:oejw.WebAppContext:main: Failed startup of context
o.e.j.w.WebAppContext@314a31b0{/,file:///tmp/jetty-0.0.0.0-8080-catalog-be-1.2.0-SNAPSHOT.war-_catalog-be-1.2.0-SNAPSHOT-any-2476064858525899818.dir/webapp/,UNAVAILABLE}{/catalog-be-1.2.0-SNAPSHOT.war}<mailto:o.e.j.w.WebAppContext@314a31b0%7b/,file:///tmp/jetty-0.0.0.0-8080-catalog-be-1.2.0-SNAPSHOT.war-_catalog-be-1.2.0-SNAPSHOT-any-2476064858525899818.dir/webapp/,UNAVAILABLE%7d%7b/catalog-be-1.2.0-SNAPSHOT.war%7d>
java.lang.NullPointerException
at
org.openecomp.sdc.be.listen.BEAppContextListener.contextInitialized(BEAppContextListener.java:66)
at
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:843)
at
org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:533)
at
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:816)
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:345)
at
org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1406)
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1368)
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:778)
at
org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:262)
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:522)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.eclipse.jetty.deploy.bindings.StandardStarter.processBinding(StandardStarter.java:41)
at
org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:188)
at
org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:499)
at
org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:147)
at
org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(ScanningAppProvider.java:180)
at
org.eclipse.jetty.deploy.providers.WebAppProvider.fileAdded(WebAppProvider.java:452)
at
org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(ScanningAppProvider.java:64)
at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:610)
at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:529)
at org.eclipse.jetty.util.Scanner.scan(Scanner.java:392)
at org.eclipse.jetty.util.Scanner.doStart(Scanner.java:313)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(ScanningAppProvider.java:150)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(DeploymentManager.java:561)
at
org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:236)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131)
at org.eclipse.jetty.server.Server.start(Server.java:427)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:113)
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.server.Server.doStart(Server.java:394)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1540)
at java.security.A
Re: [onap-discuss] Amsterdam Kubernetes OOM SDC UI is not accessible
Hi Vivek,
This is a known problem with SDC initialization in amsterdam.
In order to overcome it, you should recreate SDC pods in the following order:
cs -> be -> fe.
Example, if my namespace is onap, I would:
# kubectl delete pod -n onap-sdc sdc-cs-fd787c9b6-nt6f2
Wait for another instance of sdc-cs pod to be created and running (1/1)
# kubectl delete pod -n onap-sdc sdc-be-6644d5cd67-vg4xw
Wait for another instance of sdc-be pod to be created and running (2/2)
#kubectl delete pod -n onap-sdc sdc-fe-7c4d59c5dc-5d5qw
Wait for another instance of sdc-fe pod to be created and running (2/2)
Hope this helps.
Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726
[amdocs-a]
Amdocs a Platinum member of
ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap>
From: onap-discuss-boun...@lists.onap.org
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Vivekanandan
Muthukrishnan
Sent: Friday, March 2, 2018 6:41 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Amsterdam Kubernetes OOM SDC UI is not accessible
Hi All,
We are setting up Amsterdam kuberneter oom. The deployment went fine, even the
ONAP portal login works fine.
However when we try to access the SDC portal it is keep throwing 503 error
message. And we looked at the SDC-BE and SDC-ES logs and it seems like the
elastic serach container failed to initialise "Error :
Chef::Exceptions::FileNotFound: Cookbook 'sdc-elasticsearch' (0.0.0)"
Did anyone face this issue? Is there any workaround to over come this issue?
Thanks & Regards
Vivek
SDC-ES log sinppets
[2018-02-28T12:24:38+00:00] INFO: Running queued delayed notifications before
re-raising exception
Running handlers:
[2018-02-28T12:24:38+00:00] ERROR: Running exception handlers
Running handlers complete
[2018-02-28T12:24:38+00:00] ERROR: Exception handlers complete
Chef Client failed. 0 resources updated in 01 seconds
[2018-02-28T12:24:38+00:00] FATAL: Stacktrace dumped to
/root/chef-solo/cache/chef-stacktrace.out
[2018-02-28T12:24:38+00:00] FATAL: Please provide the contents of the
stacktrace.out file if you file a bug report
[2018-02-28T12:24:38+00:00] ERROR:
cookbook_file[/usr/share/elasticsearch/config/kibana_dashboard_virtualization.json]
(sdc-elasticsearch::ES_6_create_kibana_dashboard_virtualization line 1) had an
error: Chef::Exceptions::FileNotFound: Cookbook 'sdc-elasticsearch' (0.0.0)
does not contain a file at any of these locations:
files/debian-8.6/kibana_dashboard_virtualization.json
files/debian/kibana_dashboard_virtualization.json
files/default/kibana_dashboard_virtualization.json
files/kibana_dashboard_virtualization.json
This cookbook _does_ contain:
['files/default/dashboard_BI-Dashboard.json','files/default/dashboard_Monitoring-Dashboared.json','files/default/logging.yml','files/default/visualization_JVM-used-CPU.json','files/default/visualization_JVM-used-Memory.json','files/default/visualization_Show-all-certified-services-ampersand-resources-(per-day).json','files/default/visualization_Show-all-created-Resources-slash-Services-slash-Products.json','files/default/visualization_host-used-CPU.json','files/default/visualization_host-used-Threads-Num.json','files/default/visualization_number-of-user-accesses.json','files/default/visualization_Show-all-distributed-services.json','files/default/visualization_JVM-used-Threads-Num.json']
[2018-02-28T12:24:38+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef
run process exited unsuccessfully (exit code 1)
[2018-02-28 12:39:06,607][INFO ][cluster.metadata ]
[sdc-es-3319302712-dn5h1] [.kibana] creating index, cause [api], templates [],
shards [1]/[1], mappings [config]
SDC-BE log snippets
2018-02-28T17:40:21.169Z[ES-Health-Check-Thread]ERROR
o.o.sdc.be.dao.impl.ESCatalogDAOError while trying to c
onnect to elasticsearch. host: [sdc-es.onap-sdc:9300] | port: 9200 | error:
None of the configured nodes are available: [{#transport#-1}{10.42.
82.207}{sdc-es.onap-sdc/10.42.82.207:9300<http://10.42.82.207:9300/>}]
ONAP Portl UI
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
<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] [openlab] Cannot connect to instances in OpenLab
Hi Stephen, When I create an instance in Windriver Openstack, I cannot connect to its ip. I created VM: borislav-oom-rancher<http://10.12.25.2/project/instances/c90b5ba0-468c-4848-9de0-451bf677a00b/> with IP: 10.12.5.152 in OOM project (on external network, cannot create any other routable ip). Can't ping the IP from the Jump Station. Please kindly assist! I created a task in OpenLab project: OPENLABS-182<https://jira.onap.org/browse/OPENLABS-182> Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-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 <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] [OOM] restart an entire POD ?
Thanks. What is the correct order? We will take care of enforcing it. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap> From: FREEMAN, BRIAN D [mailto:bf1...@att.com] Sent: Wednesday, February 7, 2018 7:33 PM To: Borislav Glozman <borislav.gloz...@amdocs.com>; Mandeep Khinda <mandeep.khi...@amdocs.com>; Alexis de Talhouët <adetalhoue...@gmail.com> Cc: onap-discuss@lists.onap.org Subject: RE: [onap-discuss] [OOM] restart an entire POD ? AAI Brian k8s_aai-service_aai-service-749944520-qqs7m_onap-aai_4e885d69-0c18-11e8-acd3-02f29cda8767_0 k8s_aai-traversal_aai-traversal-140815912-xpmkn_onap-aai_4ebfdced-0c18-11e8-acd3-02f29cda8767_0 k8s_aai-resources_aai-resources-4188957633-28fns_onap-aai_4e7ee05b-0c18-11e8-acd3-02f29cda8767_0 k8s_data-router_data-router-3700447603-n4q2x_onap-aai_4ee40c1c-0c18-11e8-acd3-02f29cda8767_0 k8s_model-loader-service_model-loader-service-911950978-2k6vz_onap-aai_4e945d5f-0c18-11e8-acd3-02f29cda8767_0 k8s_elasticsearch_elasticsearch-622738319-5f71z_onap-aai_4f1ec5be-0c18-11e8-acd3-02f29cda8767_0 k8s_search-data-service_search-data-service-2471976899-z2zxf_onap-aai_4ea070c4-0c18-11e8-acd3-02f29cda8767_0 k8s_sparky-be_sparky-be-1779663793-z9qj5_onap-aai_4ea7cb7f-0c18-11e8-acd3-02f29cda8767_0 k8s_hbase_hbase-3471984843-hg3pw_onap-aai_4e919e66-0c18-11e8-acd3-02f29cda8767_0 k8s_esr-esrserver_esr-esrserver-1044617554-0hk2k_onap-esr_c12b3c4d-0ac6-11e8-acd3-02f29cda8767_0 k8s_esr-esrgui_esr-esrgui-1816310556-lw69v_onap-esr_c1297dd7-0ac6-11e8-acd3-02f29cda8767_0 -Original Message- From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com] Sent: Wednesday, February 07, 2018 10:46 AM To: FREEMAN, BRIAN D <bf1...@att.com<mailto:bf1...@att.com>>; Mandeep Khinda <mandeep.khi...@amdocs.com<mailto:mandeep.khi...@amdocs.com>>; Alexis de Talhouët <adetalhoue...@gmail.com<mailto:adetalhoue...@gmail.com>> Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: RE: [onap-discuss] [OOM] restart an entire POD ? It is possible to define an order by using readinessCheck init container. It is done in many places like sdc (although there are other problems there that should be solved soon by SDC project) Which component is 8 containers? Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 Amdocs a Platinum member of ONAP -Original Message- From: FREEMAN, BRIAN D [mailto:bf1...@att.com] Sent: Wednesday, February 7, 2018 5:43 PM To: Borislav Glozman <borislav.gloz...@amdocs.com<mailto:borislav.gloz...@amdocs.com>>; Mandeep Khinda <mandeep.khi...@amdocs.com<mailto:mandeep.khi...@amdocs.com>>; Alexis de Talhouët <adetalhoue...@gmail.com<mailto:adetalhoue...@gmail.com>> Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: RE: [onap-discuss] [OOM] restart an entire POD ? Agree and for simple components I do that. When there are 8 pods in a component getting the order correct is important/a pain. Brian -Original Message- From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com] Sent: Wednesday, February 07, 2018 10:41 AM To: Mandeep Khinda <mandeep.khi...@amdocs.com<mailto:mandeep.khi...@amdocs.com>>; FREEMAN, BRIAN D <bf1...@att.com<mailto:bf1...@att.com>>; Alexis de Talhouët <adetalhoue...@gmail.com<mailto:adetalhoue...@gmail.com>> Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: RE: [onap-discuss] [OOM] restart an entire POD ? What I do to bounce a pod is just deleting it. Helm will recreate it by itself. Example: root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl get pods -n onap-mso NAME READY STATUSRESTARTS AGE mariadb-6487b74997-9hcpg 1/1 Running 0 2d mso-6d6f86958b-n2h7p 2/2 Running 0 2d root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl delete po -n onap-mso mso-6d6f86958b-n2h7p pod "mso-6d6f86958b-n2h7p" deleted root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl get pods -n onap-mso -w NAME READY STATUSRESTARTS AGE mariadb-6487b74997-9hcpg 1/1 Running 0 2d mso-6d6f86958b-l7tk9 0/2 Init:0/1 0 2s mso-6d6f86958b-n2h7p 2/2 Terminating 0 2d mso-6d6f86958b-n2h7p 0/2 Terminating 0 2d mso-6d6f86958b-l7tk9 0/2 Init:0/1 0 13s mso-6d6f86958b-l7tk9 0/2 PodInitializing 0 17s mso-6d6f86958b-l
Re: [onap-discuss] [OOM] restart an entire POD ?
It is possible to define an order by using readinessCheck init container. It is done in many places like sdc (although there are other problems there that should be solved soon by SDC project) Which component is 8 containers? Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 Amdocs a Platinum member of ONAP -Original Message- From: FREEMAN, BRIAN D [mailto:bf1...@att.com] Sent: Wednesday, February 7, 2018 5:43 PM To: Borislav Glozman <borislav.gloz...@amdocs.com>; Mandeep Khinda <mandeep.khi...@amdocs.com>; Alexis de Talhouët <adetalhoue...@gmail.com> Cc: onap-discuss@lists.onap.org Subject: RE: [onap-discuss] [OOM] restart an entire POD ? Agree and for simple components I do that. When there are 8 pods in a component getting the order correct is important/a pain. Brian -Original Message----- From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com] Sent: Wednesday, February 07, 2018 10:41 AM To: Mandeep Khinda <mandeep.khi...@amdocs.com>; FREEMAN, BRIAN D <bf1...@att.com>; Alexis de Talhouët <adetalhoue...@gmail.com> Cc: onap-discuss@lists.onap.org Subject: RE: [onap-discuss] [OOM] restart an entire POD ? What I do to bounce a pod is just deleting it. Helm will recreate it by itself. Example: root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl get pods -n onap-mso NAME READY STATUSRESTARTS AGE mariadb-6487b74997-9hcpg 1/1 Running 0 2d mso-6d6f86958b-n2h7p 2/2 Running 0 2d root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl delete po -n onap-mso mso-6d6f86958b-n2h7p pod "mso-6d6f86958b-n2h7p" deleted root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl get pods -n onap-mso -w NAME READY STATUSRESTARTS AGE mariadb-6487b74997-9hcpg 1/1 Running 0 2d mso-6d6f86958b-l7tk9 0/2 Init:0/1 0 2s mso-6d6f86958b-n2h7p 2/2 Terminating 0 2d mso-6d6f86958b-n2h7p 0/2 Terminating 0 2d mso-6d6f86958b-l7tk9 0/2 Init:0/1 0 13s mso-6d6f86958b-l7tk9 0/2 PodInitializing 0 17s mso-6d6f86958b-l7tk9 1/2 Running 0 19s mso-6d6f86958b-l7tk9 2/2 Running 0 30s Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 Amdocs a Platinum member of ONAP -Original Message- From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Mandeep Khinda Sent: Wednesday, February 7, 2018 5:17 PM To: FREEMAN, BRIAN D <bf1...@att.com>; Alexis de Talhouët <adetalhoue...@gmail.com> Cc: onap-discuss@lists.onap.org Subject: Re: [onap-discuss] [OOM] restart an entire POD ? One negative to deleteAll and our helm charts in their current incarnation is that it deletes everything in the namespace including services (Pod and cluster IPs will change when they come back), database processes etc (not the persisted data). If you are impatient like I am, I target just the deployment I want to bounce by exporting the current running yaml and then following something similar to the link Josef had sent. For example: This is what I would use to bounce just the SO Jboss container: kubectl -n onap-mso get deployment mso -o=yaml > /tmp/mso.app.yaml kubectl -n onap-mso delete -f /tmp/mso.app.yaml kubectl -n onap-mso create -f /tmp/mso.app.yaml Mandeep Khinda Software Development Open Network Division +1.613.595.5132 (office) Read the latest on Amdocs.com <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.amdocs.com_=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=XQlpPNDe0wJW31pqXpbEZL8hMiyEikP3zy-m4Q6t5o8=KaEcYSlWDL-NkM640m2pDRkpiioOHlsRJ33iJ1uyjio= > and the Amdocs blog network <https://urldefense.proofpoint.com/v2/url?u=http-3A__blogs.amdocs.com_=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=XQlpPNDe0wJW31pqXpbEZL8hMiyEikP3zy-m4Q6t5o8=Wx4aXKE3JvDNyTOjO2ClEltN6yvplMVTySQ_Cy7lhc0= > – and follow us on Facebook <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_Amdocs=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=XQlpPNDe0wJW31pqXpbEZL8hMiyEikP3zy-m4Q6t5o8=KcACu84azxvNNEhdWpVZoaE6zYEtvV0JaHdr791eGO0= >, Twitter <https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_Amdocs=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=XQlpPNDe0wJW31pqXpbEZL8hMiyEikP3zy-m4Q6t5o8=crrB78xq0LmL9dyACM13vb92Xz0CRVgqW1G0Yf_XdeQ= >, LinkedIn <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_company_amdocs=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=XQlpPNDe0wJW31pqXpbEZL8hMiyEikP3zy-m4Q6t5o8=rkIIA95JYA8HIqi5TrNmFmLMkZRAjerE6Pc-3XxjLeo= > and YouTube <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.youtube.com_amdocs=Dw
Re: [onap-discuss] [OOM] restart an entire POD ?
What I do to bounce a pod is just deleting it. Helm will recreate it by itself. Example: root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl get pods -n onap-mso NAME READY STATUSRESTARTS AGE mariadb-6487b74997-9hcpg 1/1 Running 0 2d mso-6d6f86958b-n2h7p 2/2 Running 0 2d root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl delete po -n onap-mso mso-6d6f86958b-n2h7p pod "mso-6d6f86958b-n2h7p" deleted root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl get pods -n onap-mso -w NAME READY STATUSRESTARTS AGE mariadb-6487b74997-9hcpg 1/1 Running 0 2d mso-6d6f86958b-l7tk9 0/2 Init:0/1 0 2s mso-6d6f86958b-n2h7p 2/2 Terminating 0 2d mso-6d6f86958b-n2h7p 0/2 Terminating 0 2d mso-6d6f86958b-l7tk9 0/2 Init:0/1 0 13s mso-6d6f86958b-l7tk9 0/2 PodInitializing 0 17s mso-6d6f86958b-l7tk9 1/2 Running 0 19s mso-6d6f86958b-l7tk9 2/2 Running 0 30s Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 Amdocs a Platinum member of ONAP -Original Message- From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Mandeep Khinda Sent: Wednesday, February 7, 2018 5:17 PM To: FREEMAN, BRIAN D <bf1...@att.com>; Alexis de Talhouët <adetalhoue...@gmail.com> Cc: onap-discuss@lists.onap.org Subject: Re: [onap-discuss] [OOM] restart an entire POD ? One negative to deleteAll and our helm charts in their current incarnation is that it deletes everything in the namespace including services (Pod and cluster IPs will change when they come back), database processes etc (not the persisted data). If you are impatient like I am, I target just the deployment I want to bounce by exporting the current running yaml and then following something similar to the link Josef had sent. For example: This is what I would use to bounce just the SO Jboss container: kubectl -n onap-mso get deployment mso -o=yaml > /tmp/mso.app.yaml kubectl -n onap-mso delete -f /tmp/mso.app.yaml kubectl -n onap-mso create -f /tmp/mso.app.yaml Mandeep Khinda Software Development Open Network Division +1.613.595.5132 (office) Read the latest on Amdocs.com <http://www.amdocs.com/> and the Amdocs blog network <http://blogs.amdocs.com/> – and follow us on Facebook <http://www.facebook.com/Amdocs>, Twitter <http://twitter.com/Amdocs>, LinkedIn <http://www.linkedin.com/company/amdocs> and YouTube <http://www.youtube.com/amdocs>. On 2018-02-07, 10:00 AM, "onap-discuss-boun...@lists.onap.org on behalf of FREEMAN, BRIAN D" <onap-discuss-boun...@lists.onap.org on behalf of bf1...@att.com> wrote: OK I assume deleteAll.sh does not remove the dockernfs so persistant data should not be lost just any "fixes" to the container config. I can work with that. Brian -Original Message- From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com] Sent: Wednesday, February 07, 2018 9:56 AM To: FREEMAN, BRIAN D <bf1...@att.com> Cc: onap-discuss@lists.onap.org; Mike Elliott <mike.elli...@amdocs.com> Subject: Re: [onap-discuss] [OOM] restart an entire POD ? Hi Brian, Those issues are tracked in JIRA already. Adding Mike that is looking at it (I think). About your question, you cannot do this through K8S UI; at least, not that I’m aware of. But using our scripts, you can delete and create a specific app. For instance: ./oom/kubernetes/oneclick/deleteAll.sh -n onap -a aai <— will delete the whole AAI namespace (deployment and services) ./oom/kubernetes/oneclick/createAll.sh -n onap -a aai <— will create the whole AAI namespace (deployment and services) I’m not sure this is what you’re after, but that’s how I do it when I need to bounce a whole application (e.g. all the containers of an app). Alexis > On Feb 7, 2018, at 9:34 AM, FREEMAN, BRIAN D <bf1...@att.com> wrote: > > Michael, Alexi, > > I'm having race conditions when I use OOM in Azure where the health check passes but distribution fails (MSO and AAI never get notified). > > I restarted the SO front end POD and SO successfully picked up a model distribution. > > I tried to restart just the AAI Model loader but that didnt seem to work so I need to restart all of AAI > > I suspect that SO and AAI came up before DMaaP was up but cant confirm that. > > Is there an easy / safe way to do restart an entire domain through the K8 portal ? > > Feel free to point me at the right documentation
[onap-discuss] Did You Know?
[cid:image001.png@01D39363.9A0858C0] Did You Know? OOM enhances ONAP by deploying Logging framework OOM implements Logging Enhancement Project<https://wiki.onap.org/display/DW/Logging+Enhancements+Project> by deploying Elastic Stack<https://github.com/elastic> and defining consistent logging configuration. OOM deploys (ElasticSearch<https://www.elastic.co/products/elasticsearch>, Logstash<https://www.elastic.co/products/logstash>, Kibana<https://www.elastic.co/products/kibana>) together with filebeat<https://www.elastic.co/products/beats/filebeat> to collect logs from the different ONAP components. It enables components with canonical logs configuration. [cid:image004.png@01D3936D.E0D39F80] You can access ONAP Logs Kibana at: http://:30253/app/kibana Components that have logs available in OOM Elastic Stack: A, APPC, MSO, Policy, Portal, SDC, SDNC, VID. If you would like ONAP to collect your components logs in a consistent matter, please contact the OOM team. If you'd like to learn more about OOM, check out the OOM wiki<https://wiki.onap.org/display/DW/ONAP+Operations+Manager+Project>. Thanks, Borislav Glozman ONAP Operations Manager Team [amdocs-a] Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-network/nfv-powered-by-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 <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] [openlab] Insufficient permissions to run vFW demo in OpenLab
Hi Stephen,
Thanks a lot!
I created my own network and vFWCL creation worked.
Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726
From: Gooch, Stephen [mailto:stephen.go...@windriver.com]
Sent: Thursday, January 18, 2018 11:44 AM
To: Borislav Glozman <borislav.gloz...@amdocs.com>
Cc: onap-discuss <onap-discuss@lists.onap.org>
Subject: RE: [onap-discuss] [openlab] Insufficient permissions to run vFW demo
in OpenLab
Hello Borislav,
The network you are connecting to, oam_onap_6Gve, is owned by the VIM user.
The network is shared, and is setup for DHCP to use the full range. Therefore
your tenant ID can connect to the network and receive a DHCP address. However
you will not be able to create a port with a fixed IP in the VIM user's network.
How are others implementing this use case?
Br,
- Stephen
From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com]
Sent: Wednesday, January 17, 2018 18:44
To: Gooch, Stephen
Cc: onap-discuss
Subject: [onap-discuss] [openlab] Insufficient permissions to run vFW demo in
OpenLab
Hello Stephen,
I am failing to run vFWCL demo in OpenLab.
The failure is during creation of a port with a fixed IP address.
Could you please help me resolve this?
I tried doing that with user BorislavG in OOM tenant.
This is the url for the stack:
http://10.12.25.2/project/stacks/stack/343ae95c-c9d9-44e1-9dff-a58430745c57/
vsn_private_1_port<http://10.12.25.2/project/stacks/stack/343ae95c-c9d9-44e1-9dff-a58430745c57/vsn_private_1_port/>
OS::Neutron::Port
10 minutes
Create Failed
Forbidden: resources.vsn_private_1_port: (rule:create_port and
rule:create_port:fixed_ips) on {'binding:host_id':
, u'name':
u'vFW_SINC_Module1-vsn_private_1_port-b4vullkofpnz', 'allowed_address_pairs':
, u'admin_state_up': True,
u'network_id': u'1969d338-7feb-48ce-aae3-6a6ac5aa5eba', 'tenant_id':
u'dbe658c72ee7426fa979e319fd8cacc7', 'extra_dhcp_opts': None, 'description':
'', 'wrs-binding:vif_model': , 'binding:vnic_type': 'normal', 'device_owner': '', 'device_id': '',
'mac_address': ,
'binding:profile': ,
'project_id': u'dbe658c72ee7426fa979e319fd8cacc7', u'fixed_ips':
[{u'subnet_id': u'89cf097b-48bd-4356-9d67-60b88b75f378', u'ip_address':
u'10.0.100.4'}], 'network:tenant_id': u'0e148b76ee8c42f78d37013bf6b7b1ae',
'security_groups': ,
'wrs-tm:qos': None} by {'domain': None, 'project_name': u'OOM', 'tenant_name':
u'OOM', 'project_domain': None, 'timestamp': '2018-01-17 17:29:25.356700',
'auth_token': 'f58ed02c80b04e9dbb4a995d786aaea7', 'resource_uuid': None,
'is_admin': False, 'user': u'a7633ceb2b13453fba71670272f8b788', 'tenant':
u'dbe658c72ee7426fa979e319fd8cacc7', 'read_only': False, 'project_id':
u'dbe658c72ee7426fa979e319fd8cacc7', 'user_id':
u'a7633ceb2b13453fba71670272f8b788', 'show_deleted': False, 'roles':
[u'_member_'], 'user_identity': u'a7633ceb2b13453fba71670272f8b788
dbe658c72ee7426fa979e319fd8cacc7 - - -', 'tenant_id':
u'dbe658c72ee7426fa979e319fd8cacc7', 'is_admin_project': True, 'request_id':
'req-013a6d96-c6d1-4bc2-aa99-1688c025f4cf', 'user_domain': None, 'user_name':
u'BorislavG'} disallowed by policy Neutron server returns request_ids:
['req-013a6d96-c6d1-4bc2-aa99-1688c025f4cf']
Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726
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
<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] [openlab] Insufficient permissions to run vFW demo in OpenLab
Hello Stephen,
I am failing to run vFWCL demo in OpenLab.
The failure is during creation of a port with a fixed IP address.
Could you please help me resolve this?
I tried doing that with user BorislavG in OOM tenant.
This is the url for the stack:
http://10.12.25.2/project/stacks/stack/343ae95c-c9d9-44e1-9dff-a58430745c57/
vsn_private_1_port<http://10.12.25.2/project/stacks/stack/343ae95c-c9d9-44e1-9dff-a58430745c57/vsn_private_1_port/>
OS::Neutron::Port
10 minutes
Create Failed
Forbidden: resources.vsn_private_1_port: (rule:create_port and
rule:create_port:fixed_ips) on {'binding:host_id':
, u'name':
u'vFW_SINC_Module1-vsn_private_1_port-b4vullkofpnz', 'allowed_address_pairs':
, u'admin_state_up': True,
u'network_id': u'1969d338-7feb-48ce-aae3-6a6ac5aa5eba', 'tenant_id':
u'dbe658c72ee7426fa979e319fd8cacc7', 'extra_dhcp_opts': None, 'description':
'', 'wrs-binding:vif_model': , 'binding:vnic_type': 'normal', 'device_owner': '', 'device_id': '',
'mac_address': ,
'binding:profile': ,
'project_id': u'dbe658c72ee7426fa979e319fd8cacc7', u'fixed_ips':
[{u'subnet_id': u'89cf097b-48bd-4356-9d67-60b88b75f378', u'ip_address':
u'10.0.100.4'}], 'network:tenant_id': u'0e148b76ee8c42f78d37013bf6b7b1ae',
'security_groups': ,
'wrs-tm:qos': None} by {'domain': None, 'project_name': u'OOM', 'tenant_name':
u'OOM', 'project_domain': None, 'timestamp': '2018-01-17 17:29:25.356700',
'auth_token': 'f58ed02c80b04e9dbb4a995d786aaea7', 'resource_uuid': None,
'is_admin': False, 'user': u'a7633ceb2b13453fba71670272f8b788', 'tenant':
u'dbe658c72ee7426fa979e319fd8cacc7', 'read_only': False, 'project_id':
u'dbe658c72ee7426fa979e319fd8cacc7', 'user_id':
u'a7633ceb2b13453fba71670272f8b788', 'show_deleted': False, 'roles':
[u'_member_'], 'user_identity': u'a7633ceb2b13453fba71670272f8b788
dbe658c72ee7426fa979e319fd8cacc7 - - -', 'tenant_id':
u'dbe658c72ee7426fa979e319fd8cacc7', 'is_admin_project': True, 'request_id':
'req-013a6d96-c6d1-4bc2-aa99-1688c025f4cf', 'user_domain': None, 'user_name':
u'BorislavG'} disallowed by policy Neutron server returns request_ids:
['req-013a6d96-c6d1-4bc2-aa99-1688c025f4cf']
Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726
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
<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] [OOM] Persisted mariadb for policy is breaking functionality
Hi Pam, Persistent volume is a right kubernetes way to map data from the docker container to a persistent storage, so that upon removal of the container the data is not lost. Usually persistent volumes are used for databases and such. In this case we added persistent volume for policy maria-db. Hi Alexis, The persistent volume stores initial DB initialization data, which is located in config-init docker because policy maria-db (unlike any other ONAP component) docker image comes with pre-cooked data. Therefore when this data changes, we either need to update it in our config or remove the persistent volume from policy maria-db, making it vulnerable for data loss. The addition of the pre-cooked data was supposed to be short term, until it is changed by policy team. I raised a defect in Amsterdam (POLICY-207<https://jira.onap.org/browse/POLICY-207> - Policy-db image is prepared with DB schema as binary files), however it was not fixed. Pam, maybe now is a good time to address this, please see the comments of this bug. As per our immediate needs, we either need to synchronize the maria-db data or remove the PV. I am more inclined to remove it until Policy team changes their maria-db deployment. I see your review removing the PV form policy. If we remove it, we can remove it completely, including the data in kubernetes/config/docker/init/src/config/policy/mariadb/data Also remove “chmod -R 777 /config-init/$NAMESPACE/policy/mariadb/” from kubernetes/config/docker/init/config-init.sh Also remove the kubernetes/policy/templates/policy-pv-pvc.yaml file. Or we can leave them in amsterdam, up to you. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 From: de Talhouet, Alexis [mailto:alexis.de_talho...@bell.ca] Sent: Friday, January 5, 2018 6:42 PM To: DRAGOSH, PAMELA L (PAM) <pdrag...@research.att.com> Cc: Borislav Glozman <borislav.gloz...@amdocs.com>; onap-discuss <onap-discuss@lists.onap.org> Subject: Re: [onap-discuss] [OOM] Persisted mariadb for policy is breaking functionality Pam, Thanks for the information, I integrated this new version in OOM. The thing is, since I’m using this version, pdp and pap aren’t working well. I’m facing those errors, and I’m not too sure how to debug. Also, pap provisioning requests are all failing with 400. I’m trying to track down the changes that were introduced in this new docker version for policy, but I’m struggling to figure it out. Is it related to https://jira.onap.org/browse/POLICY-501 ? and https://gerrit.onap.org/r/#/q/topic:bug/355533 Could you point me to the changes included? Also, do you have any idea on the issue bellow? Thanks, Alexis 2018-01-05 16:09:39,793 [Thread-12] ERROR com.att.eelf.error ErrorDescription=This is a general error message during the process. Please check the error message for detail information server=10.42.211.178 targetEntity=POLICY partnerName=USER serviceName=PDP:PAP.register TransactionEndTimestamp=2018-01-05T16:09:39.784+00:00 StatusCode=COMPLETE TransactionElapsedTime=51558 requestId=19da70fc-0b78-4138-9ee9-5998219a0008 ClassName=org.onap.policy.pdp.rest.PapUrlResolver targetServiceName=PE Process ErrorCode=POLICY-515E TransactionBeginTimestamp=2018-01-05T16:08:48.226+00:00 statusCode=COMPLETE POLICY-515E ERROR: PAP Server FAILED: http://pap.onap-policy:9091/pap/ 2018-01-05 16:09:39,795 [Thread-12] ERROR com.att.eelf.error ErrorDescription=This is a general error message during the process. Please check the error message for detail information server=10.42.211.178 targetEntity=POLICY partnerName=USER serviceName=PDP:PAP.register TransactionEndTimestamp=2018-01-05T16:09:39.784+00:00 StatusCode=COMPLETE TransactionElapsedTime=51558 requestId=19da70fc-0b78-4138-9ee9-5998219a0008 ClassName=org.onap.policy.pdp.rest.XACMLPdpRegisterThread targetServiceName=PE Process ErrorCode=POLICY-515E TransactionBeginTimestamp=2018-01-05T16:08:48.226+00:00 statusCode=COMPLETE POLICY-515E ERROR: PE200 - System Error: Failed to get Input Stream: java.io.IOException: Server returned HTTP response code: 500 for URL: http://pap.onap-policy:9091/pap/ 2018-01-05 16:09:52,332 [http-nio-8081-exec-12] ERROR com.att.eelf.error ErrorDescription=This is a System Error. Please check the error message for detail information ErrorCategory=ERROR ClassName=org.onap.policy.pdp.rest.config.PDPApiAuth ErrorCode=POLICY-516E POLICY-516E ERROR: AAF Client Not instantiated properly.:org.onap.policy.utils.AAFPolicyException: java.lang.reflect.InvocationTargetException - \tat org.onap.policy.utils.AAFPolicyClient.getInstance(AAFPolicyClient.java:37) - \tat org.onap.policy.pdp.rest.config.PDPApiAuth.setProperty(PDPApiAuth.java:70) - \tat org.onap.policy.pdp.rest.config.PDPApiAuth.getEnvironment(PDPApiAuth.java:81) - \tat org.onap.policy.pdp.rest.restAuth.PDPAuthenticationFilter.doFilter(PDPAuthenticationFilter.java:70) - \tat org.apache.catalina.core.ApplicationFilt
Re: [onap-discuss] [portal] what's the default login id and password for portal login page
Hi, Portal: demo/demo123456! or cs0008/demo123456! VNC: Password https://wiki.onap.org/display/DW/vFW+instantiation+E2E+-+OOM+with+OpenStack https://wiki.onap.org/display/DW/ONAP+on+Kubernetes?focusedCommentId=16009105#comment-16009105 Thanks, Borislav Glozman From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Li, Jeffrey (NSB - CN/Chengdu) Sent: Wednesday, December 20, 2017 10:19 AM To: onap-discuss@lists.onap.org Subject: [onap-discuss] [portal] what's the default login id and password for portal login page Hi, I startup some components with OOM, and all the pods (of selected component) are working. I can open the portal URL, http://10.131.66.75:30215/ONAPPORTAL/login.htm, as well as I can access the vnc-portal. But I don't know what's the login id and password of the portal Can you please give some hints of how to setup the user and password of a portal? onap-aai aai-resources-969182198-wl6t4 2/2 Running 0 1d onap-aai aai-service-2886744591-1nrkk1/1 Running 0 1d onap-aai aai-traversal-1839419331-8j5dd 2/2 Running 0 1d onap-aai data-router-1706613604-zzr7j1/1 Running 0 1d onap-aai elasticsearch-3612219857-z2zxs 1/1 Running 0 1d onap-aai hbase-542843440-xwfw0 1/1 Running 0 1d onap-aai model-loader-service-1859000721-mpl40 2/2 Running 0 1d onap-aai search-data-service-818405693-7ccmt 2/2 Running 0 1d onap-aai sparky-be-2682317867-5kl5b 2/2 Running 0 1d onap-consul consul-agent-3312409084-pfcn3 1/1 Running 0 1d onap-consul consul-server-1173049560-lnc3r 1/1 Running 1 1d onap-consul consul-server-1173049560-n7dpr 1/1 Running 0 1d onap-consul consul-server-1173049560-vbr5r 1/1 Running 0 1d onap-message-router dmaap-3126594942-vbgr7 1/1 Running 0 23h onap-message-router global-kafka-666408702-qf1rj1/1 Running 0 23h onap-message-router zookeeper-624700062-pqbxf 1/1 Running 0 23h onap-policy brmsgw-2096143467-fz082 1/1 Running 0 23h onap-policy drools-703028112-622z5 2/2 Running 0 23h onap-policy mariadb-1591291034-kzjht1/1 Running 0 23h onap-policy nexus-3883429521-r11jz 1/1 Running 0 23h onap-policy pap-533225543-0x8ks 2/2 Running 0 23h onap-policy pdp-2452717573-3rtb92/2 Running 0 23h onap-portal portalapps-1675461301-fkx6t 2/2 Running 0 23h onap-portal portaldb-3482482447-j968l 2/2 Running 0 23h onap-portal portalwidgets-2369766060-q30t1 1/1 Running 0 23h onap-portal vnc-portal-168282838-cn2rq 1/1 Running 0 23h onap-robotrobot-221710220-0glm7 1/1 Running 0 22h onap-sdc sdc-be-2869061881-svf59 2/2 Running 0 23h onap-sdc sdc-cs-4246207898-69pdk 1/1 Running 0 23h onap-sdc sdc-es-3705942430-2qnv1 1/1 Running 0 23h onap-sdc sdc-fe-617623458-8r4pw 2/2 Running 0 23h onap-sdc sdc-kb-747788738-ckghs 1/1 Running 0 23h onap-vid vid-mariadb-857798616-40k5b 1/1 Running 0 23h onap-vid vid-server-1339223572-s3hk3 2/2 Running 0 23h As I troubleshooting, some container are fetching the code/configure/library from git/marven repository, e.g. AAI-resource. This cause startup failure in an environment with proxy, we have to setup the deployment.yaml manually with the updated proxy. I suggestion that all docker images should be self-sufficient, without online download from public network and compile in RTE. Br Jeffrey 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 <https://www.amdocs.com/about/email-disclaimer> ___ onap-discuss mailing list onap-discuss@lists.onap.org
Re: [onap-discuss] [oom] Setup "local" Docker registry for Kubernetes-based installation
Hi Peter, I think that for your immediate needs you can do 'sed' on the values.yaml files and replace nexus3.onap.org with your docker registry. Do not forget the oneclick/setenv file, there is an environment variable ONAP_DOCKER_REGISTRY as well. There is a change in the oven that should make this easier in the future, you are welcome to look at the reviews in oom gerrit. Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 -Original Message- From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Piotr Jaszczyk Sent: Thursday, December 14, 2017 11:43 AM To: onap-discuss@lists.onap.org Subject: [onap-discuss] [oom] Setup "local" Docker registry for Kubernetes-based installation Hello, We are trying to install ONAP on our internal Eucalyptus-based cloud (AWS interface). So far we've created a Terraform setup which is creating "Kubernetes on Rancher" cluster, as described in the wiki. To minimize startup time I want to prepull docker images to our cloud-local Docker registry. I'd like to avoid prepulling all images to all K8s nodes every time a new cloud is created. The CI pipeline is already defined (docker pull using script from OOM-328 + docker tag + docker push) and is able to synchronize images. Now I want to use Helm setup so I can deploy apps on a specific K8s cluster but I want to use our local registry as the image-source. AFAIK images' names are defined in `values.yaml` files but there I can see no strict convention about the naming of keys in "image" section, ie. sometimes the value contains full docker image with version and sometimes version is specified separately. My initial thought would be to convert existing `values` files using some script. Without any clear convention such script would be prone to errors in the future. A cleaner solution would be to prepare OOM@K8s for such scenario, eg. by specifing a variable (like dockerRegistry) in one place. How would you suggest to proceed? Best regards, Peter J. -- Piotr Jaszczyk Engineer, Software Development Java MANO SOAM 1 R WRO 12 - ONAP squad Nokia Poland, Wrocław, West Gate ___ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss 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 <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] [oom] Issue in ONAP Amsterdam release installation
It looks like a bug that was recently introduced in aai-resources. There is already a fix thanks to Alexis in oom: https://gerrit.onap.org/r/#/c/25955/, done on 9/Dec. Please use latest oom release-1.1.0 Regarding SDC, from the screenshot it looks like it takes long time pulling the image (it is quite large...) Hopefully until now it got solved. Anyway, if you encountered a problem to access sdc (503), you should recreate sdc pods (just delete them, helm will create them for you: sdc-cs, sdc-be, sdc-fe in this order). Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 From: Potter, Nathaniel [mailto:nathaniel.pot...@intel.com] Sent: Tuesday, December 12, 2017 8:29 PM To: Borislav Glozman <borislav.gloz...@amdocs.com>; Pavithra R13 <pavithra_...@infosys.com>; onap-discuss@lists.onap.org Subject: RE: [onap-discuss] [oom] Issue in ONAP Amsterdam release installation 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> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Borislav Glozman Sent: Tuesday, December 12, 2017 3:13 AM To: Pavithra R13 <pavithra_...@infosys.com<mailto:pavithra_...@infosys.com>>; onap-discuss@lists.onap.org<mailto: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<mailto:onap-discuss@lists.onap.org>; Borislav Glozman <borislav.gloz...@amdocs.com<mailto:borislav.gloz...@amdocs.com>> 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 <borislav.gloz...@amdocs.com<mailto:borislav.gloz...@amdocs.com>> Date: 11 December 2017 at 5:54:01 PM IST To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>, Pavithra R13 <pavithra_...@infosys.com<mailto:pav
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 <borislav.gloz...@amdocs.com> 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 <borislav.gloz...@amdocs.com<mailto:borislav.gloz...@amdocs.com>> Date: 11 December 2017 at 5:54:01 PM IST To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>, Pavithra R13 <pavithra_...@infosys.com<mailto:pavithra_...@infosys.com>> 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> [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<mailto: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 <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
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 <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
Hi, Please add [oom] in subject. Please pull the latest oom code, tpl was removed from log/templates/kibana-deployment.yaml in order to support helm 2.3 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: Thursday, November 23, 2017 2:01 PM To: onap-discuss@lists.onap.org Subject: [onap-discuss] Issue in ONAP Amsterdam release installation Hi, We are trying to setup ONAP Amsterdam release and we are facing the below error during log component installation(./createAll.bash -n onap -a log). Error: parse error in "log/templates/kibana-deployment.yaml": template: log/templates/kibana-deployment.yaml:71: function "tpl" not defined The command helm returned with error code 1 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 <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] [Amsterdam][OOM] step by step vFW instantiation recipe + videos
Alexis, Michael, thank you very much, this is a great achievement! Thanks, Borislav Glozman From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Michael O'Brien Sent: Sunday, December 3, 2017 4:20 PM To: Alexis de Talhouët <adetalhoue...@gmail.com>; onap-discuss@lists.onap.org Subject: Re: [onap-discuss] [Amsterdam][OOM] step by step vFW instantiation recipe + videos Alexis, Excellent, thank you all your detailed help running OOM on Friday during most of the day and the 3 days before that. The additional work retrofitting the new procedures into the concise wiki below is greatly appreciated. We are in good shape on both OOM and HEAT now for the KubeCon conference this week and the F2F ONAP conference the week after. /michael From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alexis de Talhouët Sent: Friday, December 1, 2017 19:07 To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: [onap-discuss] [Amsterdam][OOM] step by step vFW instantiation recipe + videos Hello ONAPers, Good news, we finally have the Amsterdam code base ready for the vFW instantiation. Note, the close loop has not been tested yet. Here is the wiki page to help you setup your infrastructure: https://wiki.onap.org/display/DW/OOM+Infrastructure+setup Here is the wiki page providing step by step tutorial to instantiate vFW using OOM: https://wiki.onap.org/display/DW/vFW+instantiation+E2E+-+OOM+with+OpenStack Thanks, Alexis 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 <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] [oom] How to add new entires in DNS
Hi, Kubernetes has dns support. You can use service.namespace and it will be resolved to the correct instance. It is even load-balanced (if needed). Please check documentation (it is actually very good for k8s): https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/ 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 Kanagaraj Manickam Sent: Tuesday, September 5, 2017 10:03 AM To: onap-discuss@lists.onap.org Subject: [onap-discuss] [oom] How to add new entires in DNS Dear OOM team, In HEAT based ONAP deployment, we had DNS server, where all ONAP components registers its DNS name. Similarly in OOM, I am looking for option to configure the DNS entry for CLI. Could you please help on how to add the DNS entries for ONAP components being introduced newly in the amesterdam release. Thank you. Regards Kanagaraj M *** 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！** *** This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! *** 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 <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] [oom][cli] CLI deployment from OOM
Hi Michael, We already started committing code for logging deployment, please sync with Itay on this. Let's push this through code review and approval to submit. Thanks, Borislav Glozman +972-9-7669188 +972-52-2835726 -Original Message- From: Michael O'Brien [frank.obr...@amdocs.com] Received: Monday, 28 Aug 2017, 14:36 To: Borislav Glozman [borislav.gloz...@amdocs.com]; onap-discuss@lists.onap.org [onap-discuss@lists.onap.org]; kanagaraj.manic...@huawei.com [kanagaraj.manic...@huawei.com] CC: Geora Barsky [geo...@amdocs.com] Subject: RE: [oom][cli] CLI deployment from OOM Kanagaraj, Hi, this is Michael from the OOM and Logging teams, we are also interested/involved in bringing up DCAE 1.0 in OOM �C several of us work closely with Borislav as well. We can collaborate with you and the CLI/Portals team �C as we would like to close off getting the new docker images for DCAE running this week �C both of our teams can streamline the procedure. This work also relates to the Logging team’s work bringing in the new logging component pods to OOM. We have the same goals in adding a new component to OOM. DCAE 1.0 (Ours) https://jira.onap.org/browse/OOM-5 Logging https://jira.onap.org/browse/LOG-3 CLI/Portal (yours)? https://jira.onap.org/browse/CLI-14 DCAE 1.1 https://jira.onap.org/browse/OOM-107 Thank you /michael From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Borislav Glozman Sent: Monday, August 28, 2017 03:38 To: onap-discuss@lists.onap.org; kanagaraj.manic...@huawei.com Subject: Re: [onap-discuss] [oom][cli] CLI deployment from OOM Hi, With pleasure. I am on vacation now, will do that in the beginning of next week. Thanks, Borislav Glozman +972-9-7669188 +972-52-2835726 -Original Message- From: Kanagaraj Manickam [kanagaraj.manic...@huawei.com] Received: Monday, 28 Aug 2017, 10:21 To: Borislav Glozman [borislav.gloz...@amdocs.com]; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> [onap-discuss@lists.onap.org] Subject: RE: [oom][cli] CLI deployment from OOM Dear Borislav Glozman Last week we were able to make CLI available as docker image as onap/cli-1.0-STAGING-latest. And we would like to install CLI as part of Portal component. Can you please help to make required changes in OOM. Thanks Kanagaraj M *** 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！** *** This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! *** From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com] Sent: Sunday, August 06, 2017 8:18 PM To: Kanagaraj Manickam; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: RE: [oom][cli] CLI deployment from OOM Hi, 1. You need to create a directory with all your products and also write a Dockerfile descriptor. You can take a look at other projects and do similar in sdnc project (like sdnc/oam/installation/sdnc) a. Take a look at the docker file: sdnc\oam\installation\sdnc\src\main\docker\Dockerfile b. Take a look at the pom: sdnc\oam\installation\sdnc\pom.xml i. You will find here docker-maven-plugin among others. ii. Then you can run a maven (something like mvn deploy) command in Jenkins and the images will be created and uploaded. 2. Once you will have a docker image (produced from 1.), I can help you with the k8s deployment. a. You can look at an example of sdnc deployment descriptors at oom project: oom\kubernetes\sdnc\*.yaml files Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 From: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com] Sent: Friday, August 4, 2017 7:46 AM To: Borislav Glozman <borislav.gloz...@amdocs.com<mailto:borislav.gloz...@amdocs.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: RE: [oom][cli] CLI deployment from OOM Hi Borislav Glozman, We would like to deploy the CLI as part of OOM ONAP deployment and we are currently investigating
Re: [onap-discuss] [oom][cli] CLI deployment from OOM
Hi, With pleasure. I am on vacation now, will do that in the beginning of next week. Thanks, Borislav Glozman +972-9-7669188 +972-52-2835726 -Original Message- From: Kanagaraj Manickam [kanagaraj.manic...@huawei.com] Received: Monday, 28 Aug 2017, 10:21 To: Borislav Glozman [borislav.gloz...@amdocs.com]; onap-discuss@lists.onap.org [onap-discuss@lists.onap.org] Subject: RE: [oom][cli] CLI deployment from OOM Dear Borislav Glozman Last week we were able to make CLI available as docker image as onap/cli-1.0-STAGING-latest. And we would like to install CLI as part of Portal component. Can you please help to make required changes in OOM. Thanks Kanagaraj M *** 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！** *** This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! *** From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com] Sent: Sunday, August 06, 2017 8:18 PM To: Kanagaraj Manickam; onap-discuss@lists.onap.org Subject: RE: [oom][cli] CLI deployment from OOM Hi, 1. You need to create a directory with all your products and also write a Dockerfile descriptor. You can take a look at other projects and do similar in sdnc project (like sdnc/oam/installation/sdnc) a. Take a look at the docker file: sdnc\oam\installation\sdnc\src\main\docker\Dockerfile b. Take a look at the pom: sdnc\oam\installation\sdnc\pom.xml i. You will find here docker-maven-plugin among others. ii. Then you can run a maven (something like mvn deploy) command in Jenkins and the images will be created and uploaded. 2. Once you will have a docker image (produced from 1.), I can help you with the k8s deployment. a. You can look at an example of sdnc deployment descriptors at oom project: oom\kubernetes\sdnc\*.yaml files Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 From: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com] Sent: Friday, August 4, 2017 7:46 AM To: Borislav Glozman <borislav.gloz...@amdocs.com<mailto:borislav.gloz...@amdocs.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: RE: [oom][cli] CLI deployment from OOM Hi Borislav Glozman, We would like to deploy the CLI as part of OOM ONAP deployment and we are currently investigating on making the required changes for building CLI docker as part of CI. So could you please help us 1. How to create the docker image for CLI as part of Jenkins CLI 2. How to create the k8s deployment ? Thanks Kanagaraj M *** 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！** *** This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! *** From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com] Sent: 03 August 2017 16:13 To: Kanagaraj Manickam; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: RE: [oom][cli] CLI deployment from OOM Hi Kanagaraj, What exactly would you like to deploy? Is there a docker image for it? Is there Dockerfile? I will be glad to assist with the k8s deployment. 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&
[onap-discuss] [OOM] Partial commits to gerrit
Hi, I see a partial commit from 16/Aug: onap 1.1 deployment files work in progress... This commit breaks functionality. Let's commit partial work in a feature branch so that it will not block work of other committers. Could this commit please be reverted? Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 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 <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] [oom][cli] CLI deployment from OOM
Hi, 1. You need to create a directory with all your products and also write a Dockerfile descriptor. You can take a look at other projects and do similar in sdnc project (like sdnc/oam/installation/sdnc) a. Take a look at the docker file: sdnc\oam\installation\sdnc\src\main\docker\Dockerfile b. Take a look at the pom: sdnc\oam\installation\sdnc\pom.xml i. You will find here docker-maven-plugin among others. ii. Then you can run a maven (something like mvn deploy) command in Jenkins and the images will be created and uploaded. 2. Once you will have a docker image (produced from 1.), I can help you with the k8s deployment. a. You can look at an example of sdnc deployment descriptors at oom project: oom\kubernetes\sdnc\*.yaml files Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 From: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com] Sent: Friday, August 4, 2017 7:46 AM To: Borislav Glozman <borislav.gloz...@amdocs.com>; onap-discuss@lists.onap.org Subject: RE: [oom][cli] CLI deployment from OOM Hi Borislav Glozman, We would like to deploy the CLI as part of OOM ONAP deployment and we are currently investigating on making the required changes for building CLI docker as part of CI. So could you please help us 1. How to create the docker image for CLI as part of Jenkins CLI 2. How to create the k8s deployment ? Thanks Kanagaraj M *** 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！** *** This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! *** From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com] Sent: 03 August 2017 16:13 To: Kanagaraj Manickam; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: RE: [oom][cli] CLI deployment from OOM Hi Kanagaraj, What exactly would you like to deploy? Is there a docker image for it? Is there Dockerfile? I will be glad to assist with the k8s deployment. 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> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kanagaraj Manickam Sent: Thursday, August 3, 2017 9:32 AM To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: [onap-discuss] [oom][cli] CLI deployment from OOM Dear OOM team, We are from CLI project and for creating the deployment of CLI from OOM, we would like to collaborate with your team. Could you please guide us to make required implementation in OOM. Thanks Regards Kanagaraj M *** 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！** *** This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! *** 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 <https://www.amdocs.com/about/email-disclaimer> ___
Re: [onap-discuss] [OOM] Using OOM kubernetes based seed code over Rancher
Hi,
The implementation of secrets under review allows to provide passwords as
environment variables.
There are default passwords that are used in secrets for the case when the env
vars are not set.
I don’t think ONAP deployment should be coupled with Rancher.
In case of Rancher we can do without secrets.
On different deployments of k8s we need them.
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 Jason Hunt
Sent: Thursday, August 3, 2017 1:22 AM
To: Mandeep Khinda <mandeep.khi...@amdocs.com>
Cc: onap-discuss@lists.onap.org; onap-discuss-boun...@lists.onap.org
Subject: Re: [onap-discuss] [OOM] Using OOM kubernetes based seed code over
Rancher
A couple of thoughts on this, as I've had some of the same issues outlined
below.
I think it's very important that OOM provide as simple of an installation
process as possible -- ideally just running one script (as was initially
envisioned). Every additional step increases friction and reduces adoption by
the developer community.
Of course, this is not to say that we should embed passwords into scripts in
the git repository (see the other thread in the mailing list). Perhaps we
should ask why we have a docker registry with a password that is widely
published. But if we do require a password, perhaps the installation script
can accept the uid/password as a parameter to the script.
Regards,
Jason Hunt
Executive Software Architect, IBM
Phone: 314-749-7422
Email: djh...@us.ibm.com<mailto:djh...@us.ibm.com>
From:Mandeep Khinda
<mandeep.khi...@amdocs.com<mailto:mandeep.khi...@amdocs.com>>
To:Michael O'Brien
<frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>>, Viswa KSP
<kspviswa.git...@gmail.com<mailto:kspviswa.git...@gmail.com>>
Cc:"onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>"
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Date:08/02/2017 10:42 AM
Subject:Re: [onap-discuss] [OOM] Using OOM kubernetes based seed code
over Rancher
Sent by:
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>
We overcame docker image pull problems by configuring our docker daemons use
the “--insecure-registry” flag. You then have to docker login to each registry
that requires user/pass and then copy the generated credential file into a
location that kubelet uses.
This is why the current seed yamls did not have any need for secrets or
pre-pulling docker images and why I am reluctant to +2 docker secret changes
that are currently under review.
I’ll try and dig up the steps I used and update the wiki. Hopefully it will
unblock you Viswa.
Mandeep
From:
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Michael O'Brien
Sent: Wednesday, August 02, 2017 11:24 AM
To: Viswa KSP <kspviswa.git...@gmail.com<mailto:kspviswa.git...@gmail.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] [OOM] Using OOM kubernetes based seed code over
Rancher
Viswa,
Missed that you have config-init in your mail – so covered OK.
I stood up robot and aai on a clean VM to verify the docs (this is inside
an openstack lab behind a firewall – that has its own proxy)
Let me know if you have docker proxy issues – I would also like to
reference/doc this for others like yourselves.
Also, just verifying that you added the security workaround step – (or make
your docker repo trust all repos)
vi oom/kubernetes/oneclick/createAll.bash
create_namespace() {
kubectl create namespace $1-$2
+ kubectl --namespace $1-$2 create secret docker-registry regsecret
--docker-server=nexus3.onap.org:10001 --docker-username=docker
--docker-password=docker
--docker-email=em...@email.com<mailto:--docker-email=em...@email.com>
+ kubectl --namespace $1-$2 patch serviceaccount default -p
'{"imagePullSecrets": [{"name": "regsecret"}]}'
}
I just happen to be standing up a clean deployment on openstack – lets try
just robot – it pulls the testsuite image
root@obrienk-1:/home/ubuntu/oom/kubernetes/config# kubectl create -f
pod-config-init.yaml
pod "config-init" created
root@obrienk-1:/home/ubuntu/oom/kubernetes/config# cd ../oneclick/
root@obrienk-1:/home/ubuntu/oom/kubernetes/oneclick# ./createAll.bash -n onap
-a robot
** Creating up ONAP: robot
Creating namespaces **
namespace "onap-robot" created
secret "regsecret" created
serviceaccount "default" patched
Creating services **
service "robot" created
** Creating deployments for robot ***
Re: [onap-discuss] [oom][cli] CLI deployment from OOM
Hi Kanagaraj, What exactly would you like to deploy? Is there a docker image for it? Is there Dockerfile? I will be glad to assist with the k8s deployment. 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 Kanagaraj Manickam Sent: Thursday, August 3, 2017 9:32 AM To: onap-discuss@lists.onap.org Subject: [onap-discuss] [oom][cli] CLI deployment from OOM Dear OOM team, We are from CLI project and for creating the deployment of CLI from OOM, we would like to collaborate with your team. Could you please guide us to make required implementation in OOM. Thanks Regards Kanagaraj M *** 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！** *** This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! *** 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 <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] [OOM] Using OOM kubernetes based seed code over Rancher
Hi Wiswa, I would advise to download the images in advance via docker pull command. This is because they are large and the download takes long time. ONAP needs to be started within 10 minutes to be successful… 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 Viswa KSP Sent: Wednesday, August 2, 2017 4:57 PM To: Michael O'Brien <frank.obr...@amdocs.com> Cc: onap-discuss@lists.onap.org Subject: Re: [onap-discuss] [OOM] Using OOM kubernetes based seed code over Rancher Hi Michael, Thanks for your response. I tried again by creating InitContainer POD as suggested and also in 32G machine as suggested by Victor. But still the environment is NOT up yet for me. Only 5 PODs are running successfully. kspviswa@onap-oom:~/oom/kubernetes/oneclick$ kubectl get pods --all-namespaces | grep onap onap-aai aai-service-3351257372-8htfv0/1 ImagePullBackOff 0 36m onap-aai hbase-1381435241-xqnrq 1/1 Running 0 36m onap-aai model-loader-service-2816942467-x8581 0/1 Init:0/2 1 36m onap-appc appc-3536695022-tf21s 0/1 ImagePullBackOff 0 36m onap-appc appc-dbhost-2406136630-5ph551/1 Running 0 36m onap-appc appc-dgbuilder-4185623067-142kt 0/1 Init:Error 0 36m onap-message-router dmaap-1601351982-638d7 0/1 Init:0/1 1 36m onap-message-router global-kafka-1879814407-kpxgk 0/1 CrashLoopBackOff 9 36m onap-message-router zookeeper-1324948063-sdn0n 1/1 Running 0 36m onap-mso mariadb-756296431-890d0 0/1 ImagePullBackOff 0 36m onap-mso mso-1648770403-3ntv60/1 Init:0/1 1 36m onap-policy brmsgw-2416784739-499ht 0/1 Init:Error 0 36m onap-policy drools-3970961907-mnpwk 0/1 Init:Error 0 36m onap-policy mariadb-1486010673-pzjlq0/1 ErrImagePull 0 36m onap-policy nexus-1796544898-84c4c 0/1 Init:Error 0 36m onap-policy pap-2037709173-9f2n20/1 Init:0/2 1 36m onap-policy pdp-2518504778-cvjt40/1 Init:Error 0 36m onap-policy pypdp-2081973022-h4qsf 0/1 Init:Error 0 36m onap-portal portalapps-1161448524-hgrlq 0/1 Init:Error 0 36m onap-portal portaldb-567766617-nd4sr0/1 ErrImagePull 0 36m onap-portal vnc-portal-647462255-4d2l5 0/1 Init:0/5 1 36m onap-robotrobot-4262359493-d8dgl 0/1 ErrImagePull 0 36m onap-sdc sdc-be-4008639732-k29hg 0/1 Init:0/2 1 36m onap-sdc sdc-cs-2600616558-j9b2f 0/1 Init:Error 1 36m onap-sdc sdc-es-2988521946-1wznh 0/1 ImagePullBackOff 0 36m onap-sdc sdc-fe-2781606410-tvjbz 0/1 Init:0/1 1 36m onap-sdc sdc-kb-220921189-dntw4 0/1 Init:0/1 1 36m onap-sdnc sdnc-2444767113-v2nd5 0/1 ErrImagePull 0 36m onap-sdnc sdnc-dbhost-3342709633-2k0sr1/1 Running 0 36m onap-sdnc sdnc-dgbuilder-2456201986-b5f65 0/1 Init:0/1 1 36m onap-sdnc sdnc-portal-3781432694-9l0f60/1 Init:0/1 1 36m onap-vid vid-mariadb-344946511-dj3b6 1/1 Running 0 36m onap-vid vid-server-3905085274-g5bh9 0/1 ErrImagePull 0 36m I also see below warning on every POD. Search Line limits were exceeded, some dns names have been omitted, the applied search line is: onap-portal.svc.cluster.local svc.cluster.local cluster.local kubelet.kubernetes.rancher.internal kubernetes.rancher.internal rancher.internal Error syncing pod BTW I had edited /etc/resolv.conf as per the suggestion in Wiki. But still facing the issues. Please let me know if I had missed anything. BR, Viswa On Mon, Jul 31, 2017 at 10:25 PM, Michael O'Brien <frank.obr...@amdocs.com<mail
