Re: [onap-discuss] [ONAP Helpdesk #56451] [portal] Missing Portal docker images

[Gary Wu via RT]

I think some teams managed to produce "release-like" tags and put them into the 
docker.snapshots repo, but they were not really released via LF.

You can look up the past errors by browsing the build history for 
http://12.234.32.117/jenkins/job/nexus3-docker-image-check/. 

Some of the past ones that have disappeared:

[ERROR] onap/multicloud/vio:1.1.2-STAGING not found
[ERROR] onap/multicloud/vio-vesagent:1.0.0 not found
[ERROR] onap/multicloud/framework:1.1.2-STAGING not found
[ERROR] openecomp/mso:1.2.1 not found
[ERROR] onap/multicloud/openstack-ocata:1.1.2-SNAPSHOT not found

Thanks,
Gary

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Thursday, May 24, 2018 9:28 PM
To: Gary Wu 
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #56451] [portal] Missing Portal docker images

I am confused by the tag, these are supposed to be found in snapshots repo?
Why do they have a release tag?

Also, quick question Gary, on these disappearing images issue, does it seems 
like the only images that disappear have the release tag format? Do you recall 
any disappeared images under the SNAPSHOT or STAGING tag? I don't 

Thansk!
Jess


On Fri May 25 00:23:48 2018, jwagantall wrote:
> Investigating this issue.. 
> 
> Thanks!
> Jess
> 
> On Fri May 25 00:15:54 2018, gary.i...@huawei.com wrote:
> > Hi helpdesk and/or Portal team,
> > 
> > The following images have disappeared from nexus3:
> > 
> > 19:04:55 [ERROR] onap/portal-app:v2.2.0 not found
> > 19:04:56 [ERROR] onap/portal-db:v2.2.0 not found
> > 19:04:57 [ERROR] onap/portal-sdk:v2.2.0 not found
> > 19:04:57 [ERROR] onap/portal-wms:v2.2.0 not found
> > 
> > http://12.234.32.117/jenkins/job/nexus3-docker-image-check/321/conso
> > le
> > 
> > Please help.
> > 
> > Thanks,
> > Gary
> > 
> > 
> 
> 




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

Re: [onap-discuss] [ONAP Helpdesk #56451] [portal] Missing Portal docker images

[Gary Wu]

I think some teams managed to produce "release-like" tags and put them into the 
docker.snapshots repo, but they were not really released via LF.

You can look up the past errors by browsing the build history for 
http://12.234.32.117/jenkins/job/nexus3-docker-image-check/. 

Some of the past ones that have disappeared:

[ERROR] onap/multicloud/vio:1.1.2-STAGING not found
[ERROR] onap/multicloud/vio-vesagent:1.0.0 not found
[ERROR] onap/multicloud/framework:1.1.2-STAGING not found
[ERROR] openecomp/mso:1.2.1 not found
[ERROR] onap/multicloud/openstack-ocata:1.1.2-SNAPSHOT not found

Thanks,
Gary

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Thursday, May 24, 2018 9:28 PM
To: Gary Wu 
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #56451] [portal] Missing Portal docker images

I am confused by the tag, these are supposed to be found in snapshots repo?
Why do they have a release tag?

Also, quick question Gary, on these disappearing images issue, does it seems 
like the only images that disappear have the release tag format? Do you recall 
any disappeared images under the SNAPSHOT or STAGING tag? I don't 

Thansk!
Jess


On Fri May 25 00:23:48 2018, jwagantall wrote:
> Investigating this issue.. 
> 
> Thanks!
> Jess
> 
> On Fri May 25 00:15:54 2018, gary.i...@huawei.com wrote:
> > Hi helpdesk and/or Portal team,
> > 
> > The following images have disappeared from nexus3:
> > 
> > 19:04:55 [ERROR] onap/portal-app:v2.2.0 not found
> > 19:04:56 [ERROR] onap/portal-db:v2.2.0 not found
> > 19:04:57 [ERROR] onap/portal-sdk:v2.2.0 not found
> > 19:04:57 [ERROR] onap/portal-wms:v2.2.0 not found
> > 
> > http://12.234.32.117/jenkins/job/nexus3-docker-image-check/321/conso
> > le
> > 
> > Please help.
> > 
> > Thanks,
> > Gary
> > 
> > 
> 
> 



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

[onap-discuss] [ONAP Helpdesk #56451] [portal] Missing Portal docker images

[Jessica Wagantall via RT]

I am confused by the tag, these are supposed to be found in snapshots repo?
Why do they have a release tag?

Also, quick question Gary, on these disappearing images issue, does it seems 
like the only
images that disappear have the release tag format? Do you recall any 
disappeared images
under the SNAPSHOT or STAGING tag? I don't 

Thansk!
Jess


On Fri May 25 00:23:48 2018, jwagantall wrote:
> Investigating this issue.. 
> 
> Thanks!
> Jess
> 
> On Fri May 25 00:15:54 2018, gary.i...@huawei.com wrote:
> > Hi helpdesk and/or Portal team,
> > 
> > The following images have disappeared from nexus3:
> > 
> > 19:04:55 [ERROR] onap/portal-app:v2.2.0 not found
> > 19:04:56 [ERROR] onap/portal-db:v2.2.0 not found
> > 19:04:57 [ERROR] onap/portal-sdk:v2.2.0 not found
> > 19:04:57 [ERROR] onap/portal-wms:v2.2.0 not found
> > 
> > http://12.234.32.117/jenkins/job/nexus3-docker-image-check/321/console
> > 
> > Please help.
> > 
> > Thanks,
> > Gary
> > 
> > 
> 
> 



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

[onap-discuss] [ONAP Helpdesk #56451] [portal] Missing Portal docker images

[Jessica Wagantall via RT]

Investigating this issue.. 

Thanks!
Jess

On Fri May 25 00:15:54 2018, gary.i...@huawei.com wrote:
> Hi helpdesk and/or Portal team,
> 
> The following images have disappeared from nexus3:
> 
> 19:04:55 [ERROR] onap/portal-app:v2.2.0 not found
> 19:04:56 [ERROR] onap/portal-db:v2.2.0 not found
> 19:04:57 [ERROR] onap/portal-sdk:v2.2.0 not found
> 19:04:57 [ERROR] onap/portal-wms:v2.2.0 not found
> 
> http://12.234.32.117/jenkins/job/nexus3-docker-image-check/321/console
> 
> Please help.
> 
> Thanks,
> Gary
> 
> 



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

[onap-discuss] [portal] Missing Portal docker images

[Gary Wu]

Hi helpdesk and/or Portal team,

The following images have disappeared from nexus3:

19:04:55 [ERROR] onap/portal-app:v2.2.0 not found
19:04:56 [ERROR] onap/portal-db:v2.2.0 not found
19:04:57 [ERROR] onap/portal-sdk:v2.2.0 not found
19:04:57 [ERROR] onap/portal-wms:v2.2.0 not found

http://12.234.32.117/jenkins/job/nexus3-docker-image-check/321/console

Please help.

Thanks,
Gary


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

[onap-discuss] VID erros in OOM Beijing

[abdelmuhaimen.seaudi]

Hi,

After OOM Beijing is fully up and running, I cannot access VID, I get the 
output shown in the attached snapshot.

Although Robot health check is PASS for VID, however in CONSUL, I see VID 
MariaDb is FAILURE.

I see the following logs in the mariadb pod:
5/25/2018 12:18:22 AM2018-05-24 22:18:22 140682260137728 [Warning] Aborted 
connection 364 to db: 'vid_openecomp_epsdk' user: 'vidadmin' host: 
'10.42.205.85' (Got timeout reading communication packets)
5/25/2018 12:18:22 AM2018-05-24 22:18:22 140682259531520 [Warning] Aborted 
connection 366 to db: 'vid_openecomp_epsdk' user: 'vidadmin' host: 
'10.42.205.85' (Got timeout reading communication packets)
5/25/2018 12:18:22 AM2018-05-24 22:18:22 140682259834624 [Warning] Aborted 
connection 365 to db: 'vid_openecomp_epsdk' user: 'vidadmin' host: 
'10.42.205.85' (Got timeout reading communication packets)

How can I resolve this issue to have VID run OK ?


Thanks

A. Seaudi

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[onap-discuss] [coe] Meeting's survey

[Morales, Victor]

Hey there,

Maybe I was the only confused about the time for this meeting but it could be a 
good time to propose a different time. So please vote for the best time that 
works for you.

https://www.surveymonkey.com/r/FRSKR85

Regards,
Victor Morales
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Issue pulling image

[Gary Wu]

Hi William,

Did you do “docker login”?

docker login nexus3.onap.org:10001
username: docker
password: docker

Thanks,
Gary

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of ANAPAN-LAVALLE, 
HECTOR A
Sent: Thursday, May 24, 2018 10:56 AM
To: William Kurkian ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Issue pulling image

Hi,

This issue of not pulling images from nexus3 is usually due to many reasons. I 
would first try to see if you can manually pull the docker image first (docker 
pull 
nexus3.onap.org:10001/onap/portal-app:2.1-STAGING-latest).

If you get the same error, go browse for the image in the nexus3 gui to see if 
it’s actually in the repo 
(https://nexus3.onap.org/#browse/browse:docker.public) – docker.public is the 
repo pointing to port 10001.

If you are able to find it, it might mean that nexus3 is failing. Therefore, 
you could either try to set up your own docker proxy to pull images beforehand 
from nexus3, then point to your local docker repo instead of nexus3.

From integration team:

Setting up the apt and docker proxies is basically the following on Ubuntu 
16.04:

apt-get install apt-cacher-ng
apt-get install docker.io
docker run -d -p 5000:5000 --restart=unless-stopped --name registry -e 
REGISTRY_PROXY_REMOTEURL=https://nexus3.onap.org:10001
 registry:2

The docker proxy can take up a lot of space, so you may want to allocate a 
larger disk volume than the default flavor size.

More info on how to set this up here: 
https://docs.docker.com/registry/#basic-commands

From: 
onap-discuss-boun...@lists.onap.org 
>
 On Behalf Of William Kurkian
Sent: Tuesday, May 08, 2018 12:32 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Issue pulling image

I am trying to pull an image for the portal-app pod, but it is not working:
 Failed to pull image 
"nexus3.onap.org:10001/onap/portal-app:2.1-STAGING-latest"

I can't find an image I can pull, is there something I can do to resolve this?

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

Re: [onap-discuss] Issue pulling image

[ANAPAN-LAVALLE, HECTOR A]

Hi,

This issue of not pulling images from nexus3 is usually due to many reasons. I 
would first try to see if you can manually pull the docker image first (docker 
pull 
nexus3.onap.org:10001/onap/portal-app:2.1-STAGING-latest).

If you get the same error, go browse for the image in the nexus3 gui to see if 
it’s actually in the repo 
(https://nexus3.onap.org/#browse/browse:docker.public) – docker.public is the 
repo pointing to port 10001.

If you are able to find it, it might mean that nexus3 is failing. Therefore, 
you could either try to set up your own docker proxy to pull images beforehand 
from nexus3, then point to your local docker repo instead of nexus3.

From integration team:

Setting up the apt and docker proxies is basically the following on Ubuntu 
16.04:

apt-get install apt-cacher-ng
apt-get install docker.io
docker run -d -p 5000:5000 --restart=unless-stopped --name registry -e 
REGISTRY_PROXY_REMOTEURL=https://nexus3.onap.org:10001
 registry:2

The docker proxy can take up a lot of space, so you may want to allocate a 
larger disk volume than the default flavor size.

More info on how to set this up here: 
https://docs.docker.com/registry/#basic-commands

From: onap-discuss-boun...@lists.onap.org  
On Behalf Of William Kurkian
Sent: Tuesday, May 08, 2018 12:32 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Issue pulling image

I am trying to pull an image for the portal-app pod, but it is not working:
 Failed to pull image 
"nexus3.onap.org:10001/onap/portal-app:2.1-STAGING-latest"

I can't find an image I can pull, is there something I can do to resolve this?

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

Re: [onap-discuss] where is the rancher setup script and cd.sh sripts

[abdelmuhaimen.seaudi]

Hi,

I liked to use the 2 seperate scripts, because after rancher is setup, it gives 
me a chance to run the NFS server/client, and to add additional hosts to the 
K8S cluster, and when the cluster is ready, I can run cd.sh.

I used the one click script in this link https://jira.onap.org/browse/LOG-320, 
instead of the oom_rancher_setup.sh and cd.sh.

The one click script completed OK, and I have a running Beijing OOM 
installation, using a 3 nodes k8s cluster.

I used the NFS Master and Slave Scripts in this link 
https://wiki.onap.org/display/DW/ONAP+on+Windriver+ONAP+Developer+Cloud in 
order to synchronize the /dockerdata-nfs folder between the 3 nodes.

root@olc-bjng-1:~# kubectl get pods --all-namespaces -o wide
NAMESPACE NAMEREADY STATUS  
   RESTARTS   AGE   IP  NODE
kube-system   heapster-76b8cd7b5-mrc571/1   Running 
   0  3h10.42.144.25olc-bjng-1.novalocal
kube-system   kube-dns-5d7b4487c9-2tdk9   3/3   Running 
   0  3h10.42.93.198olc-bjng-1.novalocal
kube-system   kubernetes-dashboard-f9577fffd-7vj6w1/1   Running 
   0  3h10.42.128.41olc-bjng-1.novalocal
kube-system   monitoring-grafana-997796fcf-b7cxl  1/1   Running 
   0  3h10.42.208.121   olc-bjng-1.novalocal
kube-system   monitoring-influxdb-56fdcd96b-j5lvv 1/1   Running 
   0  3h10.42.47.202olc-bjng-1.novalocal
kube-system   tiller-deploy-54bcc55dd5-9cnv8  1/1   Running 
   0  3h10.42.190.254   olc-bjng-1.novalocal
onap  dep-config-binding-service-56fbdb8b8d-k7g72 2/2   Running 
   0  1h10.42.127.94olc-bjng-2.novalocal
onap  dep-dcae-tca-analytics-84d9b7f897-7c9cj 2/2   Running 
   0  1h10.42.120.135   olc-bjng-3.novalocal
onap  dep-dcae-ves-collector-7fc9767d6d-mlb6h 2/2   Running 
   0  1h10.42.85.48 olc-bjng-2.novalocal
onap  dep-deployment-handler-559bd74b5-n5sqf  2/2   Running 
   0  1h10.42.144.33olc-bjng-3.novalocal
onap  dep-holmes-engine-mgmt-7989c76c54-lblc5 1/1   Running 
   0  1h10.42.83.15 olc-bjng-3.novalocal
onap  dep-holmes-rule-mgmt-5bbfd7f8c9-jpgq6   1/1   Running 
   0  1h10.42.10.1  olc-bjng-1.novalocal
onap  dep-inventory-54f479c584-9jw5s  1/1   Running 
   0  1h10.42.13.229olc-bjng-1.novalocal
onap  dep-policy-handler-59774b57c-d52pp  2/2   Running 
   0  1h10.42.35.31 olc-bjng-3.novalocal
onap  dep-pstg-write-787c4bb65b-hfpjq 1/1   Running 
   0  1h10.42.0.255 olc-bjng-2.novalocal
onap  dep-service-change-handler-5d449b4c9d-7k8dq 1/1   Running 
   8  1h10.42.240.48olc-bjng-2.novalocal
onap  onap-aaf-cm-7d9cfc9db9-vxktc1/1   Running 
   0  3h10.42.101.126   olc-bjng-2.novalocal
onap  onap-aaf-cs-6684b45df5-5tcwr1/1   Running 
   0  3h10.42.134.180   olc-bjng-2.novalocal
onap  onap-aaf-fs-6c8ffb65c5-lqk7v1/1   Running 
   0  3h10.42.241.42olc-bjng-3.novalocal
onap  onap-aaf-gui-748f4d9fd4-c654r   1/1   Running 
   0  3h10.42.117.210   olc-bjng-3.novalocal
onap  onap-aaf-hello-5589f-4sp7z  1/1   Running 
   0  3h10.42.134.200   olc-bjng-2.novalocal
onap  onap-aaf-locate-5d44f6679f-7vwbp1/1   Running 
   0  3h10.42.69.129olc-bjng-3.novalocal
onap  onap-aaf-oauth-768664598-9mm7b  1/1   Running 
   0  3h10.42.118.30olc-bjng-2.novalocal
onap  onap-aaf-service-69b6f5b6b6-tmcqq   1/1   Running 
   0  3h10.42.105.243   olc-bjng-3.novalocal
onap  onap-aaf-sms-6559d77ff8-67m2l   1/1   Running 
   2  3h10.42.210.190   olc-bjng-2.novalocal
onap  onap-aaf-sms-quorumclient-0 1/1   Running 
   0  3h10.42.220.100   olc-bjng-3.novalocal
onap  onap-aaf-sms-quorumclient-1 1/1   Running 
   0  3h10.42.181.199   olc-bjng-1.novalocal
onap  onap-aaf-sms-quorumclient-2 1/1   Running 
  

Re: [onap-discuss] vFWCL instantiation problem (not allowed to create an int on ext net)

[ANAPAN-LAVALLE, HECTOR A]

I think the way to resolve this is to use the private network that gets created 
after onap instantiation (oam_network_) in the public network instead 
of the public network itself (assuming the public network is not 
provider-enabled - i.e. only supports floating IPs and not direct attachment of 
public IPs to the VM).

Also, the private network needs to have internet connectivity in order to fetch 
the items from the LF repos.

From: onap-discuss-boun...@lists.onap.org  
On Behalf Of PLATANIA, MARCO
Sent: Saturday, May 05, 2018 8:02 PM
To: Badr Eddine Aouled Yahia ; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] vFWCL instantiation problem (not allowed to create 
an int on ext net)

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
The issue is that your openstack platform is not configured to allow VMs to be 
directly attached to the external or provider network. I don't know how to 
change this configuration in openstack but I'm pretty positive that that is the 
issue.

Marco



On Sat, May 5, 2018 at 11:21 AM -0400, "Badr Eddine Aouled Yahia" 
> 
wrote:
Hello,

I am playing the vFWCL use-case on Amsterdam release and i am now on the step 
of the creation of the VF modules, i have done all the previous steps 
successfully and now i am facing this problem:
when creating the vf modules, i get number of attemps exceeded, but thes 
problems is exactly the creation of an external interface for the VMs to access 
the public net.
I watched the VMs on openstack created successefully but when it comes to 
attribute ips, it rolls back
on the mso container in var/log/ecomp/MSO/VnfAdapter/
 logs, i fount this exception "It is not allowed to create an interface on 
external network"
I doubt that there is a problem in the heat templates because i have deployed a 
simple service with a single vnf (freeRadius) with well configured resources 
and parameters (router interface, floating ip ...) in the heat templates.
In the vFW heat templates, this kid of parameters and resources is not 
specified but all the tutorials in ONAP does not add any resources or 
parameters to the vFWCL heat so i am a little bit confused.
Does anyone have an idea how to solve this problem without the need to modify 
the heats for the vFWCL with hardcoded things?
or even to what this problem could be related?
Thanks community :)
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] ONAP Setup on Baremetal using Rancher

[S, Deepak]

Hi Michael,

Yes, based on the kubectl status, We have access for the nodeport 30215 to 8989.

root@onap:~/onap/oom/kubernetes# kubectl -n onap get services|grep "portal-app"
portal-app  LoadBalancer   10.43.246.615.1.1.7  
8989:30215/TCP,8006:30213/TCP,8010:30214/TCP  32m

>>> http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_user_guide.html#accessing-the-onap-portal-using-oom-and-a-kubernetes-cluster
>>>  
based on the link  you shared, we should be able to access the portal from the 
private ip or public ip (openstack floating ip). right?

In my case private ip is 5.1.1.7 and i am access the portal from same node onap 
is deployed. 


Thanks
Deepak

On Thu, 2018-05-24 at 14:16 +, Michael O'Brien wrote:
> Hi,
>Sounds good
>You will need to access the 30215 nodeport to 8989 - this would
> allow for example 2 installs on onap on the same cluster using
> different node ports.
>The latest instructions are on - I have not launched portal since
> it was switched from the vnc-portal container a month+ ago
>http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_u
> ser_guide.html#accessing-the-onap-portal-using-oom-and-a-kubernetes-
> cluster
> 
> 
> -Original Message-
> From: S, Deepak [mailto:deepa...@intel.com] 
> Sent: Thursday, May 24, 2018 10:09 AM
> To: Michael O'Brien 
> Cc: onap-discuss@lists.onap.org; cl6...@att.com
> Subject: Re: ONAP Setup on Baremetal using Rancher
> 
> Hi Michael,
> 
> I was able to setup rancher and onap following your instruction. All
> the services looks up &  running.
> 
> But, when I try to connecting to portal (http://5.1.1.7:8989/ONAPPORT
> AL/login.htm). I get No data received :(.
> 
> root@onap:~/onap/oom/kubernetes# wget http://5.1.1.7:8989/ONAPPORTAL/
> login.htm
> --2018-05-24 19:11:41--  http://5.1.1.7:8989/ONAPPORTAL/login.htm
> Connecting to 5.1.1.7:8989... connected.
> HTTP request sent, awaiting response... No data received.
> 
> Any hints, How I can access the portal service?
>  
> root@onap:~/onap/oom/kubernetes# kubectl -n onap get services|grep
> "portal-app"
> portal-
> app  LoadBalancer   10.43.246.615.1.1.7  8989:30215/TCP,8006:3021
> 3/TCP,8010:30214/TCP  32m
> 
> 
> Thanks
> Deepak
> 
> On Tue, 2018-05-22 at 13:09 +, Michael O'Brien wrote:
> > Deepak,
> >Hi, yes the rancher install script is agnostic of the undercloud
> > (aws, azure, gce, openstack, metal) - it relies on whatever
> > template
> > provisioned an Ubuntu 16.04 VM (none in your metal case) - and a
> > post
> > script to setup the NFS share - the rancher script only sets up
> > docker, helm, kubernetes (via rancher) and configures a local
> > kubectl
> > and host registration callback - the callback can be repurposed for
> > other nodes.
> > 
> >The latest is still attached to the JIRA - for use by the
> > entrypoint for the Azure arm template for example.
> >I use the script regularly for VMWare VMs.
> > https://jira.onap.org/browse/LOG-325
> > https://gerrit.onap.org/r/#/c/47315/ 
> > https://jira.onap.org/secure/attachment/11558/oom_rancher_setup.sh
> > 
> >It has however also been merged as of last week below - where it
> > will be kept up to date in the project.
> > https://git.onap.org/logging-analytics/tree/deploy/rancher/oom_ranc
> > he
> > r_setup.sh
> > 
> >Follow the guides to configure your cluster - the openstack page
> > is fully filled out - I am still writing up manual instructions to
> > provision each cluster node - as I have been working on the
> > automated
> > script to do this -  there is an example of a client host script in
> > the wiki
> > https://wiki.onap.org/display/DW/Cloud+Native+Deployment
> > https://wiki.onap.org/display/DW/ONAP+on+Windriver+ONAP+Developer+C
> > lo
> > ud
> > 
> > 
> > /michael
> > 
> > -Original Message-
> > From: S, Deepak [mailto:deepa...@intel.com] 
> > Sent: Tuesday, May 22, 2018 4:07 AM
> > To: Michael O'Brien 
> > Subject: ONAP Setup on Baremetal using Rancher
> > 
> > Hi Frank,
> > 
> > I am setting up ONAP Setup on Baremetal using Rancher. Please let
> > me
> > know if i execute below script will install all the required pieces
> > or any other steps i need.
> > https://wiki.onap.org/display/DW/ONAP+on+Kubernetes+on+Rancher
> > 
> > 
> > git clone https://gerrit.onap.org/r/oom
> > cd oom
> > git pull https://gerrit.onap.org/r/oom refs/changes/19/32019/6
> > cd install/rancher
> > ./oom_rancher_setup.sh -b master -s 10.12.5.168 -e onap
> >  
> > 
> > Thanks
> > Deepak
> > 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
> >  > s://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 

Re: [onap-discuss] ONAP Setup on Baremetal using Rancher

[S, Deepak]

Hi Michael,

I was able to setup rancher and onap following your instruction. All the 
services looks up &  running.

But, when I try to connecting to portal 
(http://5.1.1.7:8989/ONAPPORTAL/login.htm). I get No data received :(.

root@onap:~/onap/oom/kubernetes# wget http://5.1.1.7:8989/ONAPPORTAL/login.htm
--2018-05-24 19:11:41--  http://5.1.1.7:8989/ONAPPORTAL/login.htm
Connecting to 5.1.1.7:8989... connected.
HTTP request sent, awaiting response... No data received.

Any hints, How I can access the portal service?
 
root@onap:~/onap/oom/kubernetes# kubectl -n onap get services|grep "portal-app"
portal-app  LoadBalancer   10.43.246.615.1.1.7  
8989:30215/TCP,8006:30213/TCP,8010:30214/TCP  32m


Thanks
Deepak

On Tue, 2018-05-22 at 13:09 +, Michael O'Brien wrote:
> Deepak,
>Hi, yes the rancher install script is agnostic of the undercloud
> (aws, azure, gce, openstack, metal) - it relies on whatever template
> provisioned an Ubuntu 16.04 VM (none in your metal case) - and a post
> script to setup the NFS share - the rancher script only sets up
> docker, helm, kubernetes (via rancher) and configures a local kubectl
> and host registration callback - the callback can be repurposed for
> other nodes.
> 
>The latest is still attached to the JIRA - for use by the
> entrypoint for the Azure arm template for example.
>I use the script regularly for VMWare VMs.
> https://jira.onap.org/browse/LOG-325
> https://gerrit.onap.org/r/#/c/47315/ 
> https://jira.onap.org/secure/attachment/11558/oom_rancher_setup.sh
> 
>It has however also been merged as of last week below - where it
> will be kept up to date in the project.
> https://git.onap.org/logging-analytics/tree/deploy/rancher/oom_ranche
> r_setup.sh
> 
>Follow the guides to configure your cluster - the openstack page
> is fully filled out - I am still writing up manual instructions to
> provision each cluster node - as I have been working on the automated
> script to do this -  there is an example of a client host script in
> the wiki
> https://wiki.onap.org/display/DW/Cloud+Native+Deployment
> https://wiki.onap.org/display/DW/ONAP+on+Windriver+ONAP+Developer+Clo
> ud
> 
> 
> /michael
> 
> -Original Message-
> From: S, Deepak [mailto:deepa...@intel.com] 
> Sent: Tuesday, May 22, 2018 4:07 AM
> To: Michael O'Brien 
> Subject: ONAP Setup on Baremetal using Rancher
> 
> Hi Frank,
> 
> I am setting up ONAP Setup on Baremetal using Rancher. Please let me
> know if i execute below script will install all the required pieces
> or any other steps i need.
> https://wiki.onap.org/display/DW/ONAP+on+Kubernetes+on+Rancher
> 
> 
> git clone https://gerrit.onap.org/r/oom
> cd oom
> git pull https://gerrit.onap.org/r/oom refs/changes/19/32019/6
> cd install/rancher
> ./oom_rancher_setup.sh -b master -s 10.12.5.168 -e onap
>  
> 
> Thanks
> Deepak
> 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  s://www.amdocs.com/about/email-disclaimer>

smime.p7s
Description: S/MIME cryptographic signature
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Openlab

[morgan.richomme]

Y a de la demande... (au moins 5 nouvelles demande spirent sopra et jiba) 
Je tente de gérer un peu ce matin.. 

Envoyé depuis mon téléphone Orange
_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

Re: [onap-discuss] ONAP Setup on Baremetal using Rancher

[Michael O'Brien]

Hi,
   Sounds good
   You will need to access the 30215 nodeport to 8989 - this would allow for 
example 2 installs on onap on the same cluster using different node ports.
   The latest instructions are on - I have not launched portal since it was 
switched from the vnc-portal container a month+ ago
   
http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_user_guide.html#accessing-the-onap-portal-using-oom-and-a-kubernetes-cluster


-Original Message-
From: S, Deepak [mailto:deepa...@intel.com] 
Sent: Thursday, May 24, 2018 10:09 AM
To: Michael O'Brien 
Cc: onap-discuss@lists.onap.org; cl6...@att.com
Subject: Re: ONAP Setup on Baremetal using Rancher

Hi Michael,

I was able to setup rancher and onap following your instruction. All the 
services looks up &  running.

But, when I try to connecting to portal 
(http://5.1.1.7:8989/ONAPPORTAL/login.htm). I get No data received :(.

root@onap:~/onap/oom/kubernetes# wget http://5.1.1.7:8989/ONAPPORTAL/login.htm
--2018-05-24 19:11:41--  http://5.1.1.7:8989/ONAPPORTAL/login.htm
Connecting to 5.1.1.7:8989... connected.
HTTP request sent, awaiting response... No data received.

Any hints, How I can access the portal service?
 
root@onap:~/onap/oom/kubernetes# kubectl -n onap get services|grep "portal-app"
portal-app  LoadBalancer   10.43.246.615.1.1.7  
8989:30215/TCP,8006:30213/TCP,8010:30214/TCP  32m


Thanks
Deepak

On Tue, 2018-05-22 at 13:09 +, Michael O'Brien wrote:
> Deepak,
>Hi, yes the rancher install script is agnostic of the undercloud
> (aws, azure, gce, openstack, metal) - it relies on whatever template
> provisioned an Ubuntu 16.04 VM (none in your metal case) - and a post
> script to setup the NFS share - the rancher script only sets up
> docker, helm, kubernetes (via rancher) and configures a local kubectl
> and host registration callback - the callback can be repurposed for
> other nodes.
> 
>The latest is still attached to the JIRA - for use by the
> entrypoint for the Azure arm template for example.
>I use the script regularly for VMWare VMs.
> https://jira.onap.org/browse/LOG-325
> https://gerrit.onap.org/r/#/c/47315/ 
> https://jira.onap.org/secure/attachment/11558/oom_rancher_setup.sh
> 
>It has however also been merged as of last week below - where it
> will be kept up to date in the project.
> https://git.onap.org/logging-analytics/tree/deploy/rancher/oom_ranche
> r_setup.sh
> 
>Follow the guides to configure your cluster - the openstack page
> is fully filled out - I am still writing up manual instructions to
> provision each cluster node - as I have been working on the automated
> script to do this -  there is an example of a client host script in
> the wiki
> https://wiki.onap.org/display/DW/Cloud+Native+Deployment
> https://wiki.onap.org/display/DW/ONAP+on+Windriver+ONAP+Developer+Clo
> ud
> 
> 
> /michael
> 
> -Original Message-
> From: S, Deepak [mailto:deepa...@intel.com] 
> Sent: Tuesday, May 22, 2018 4:07 AM
> To: Michael O'Brien 
> Subject: ONAP Setup on Baremetal using Rancher
> 
> Hi Frank,
> 
> I am setting up ONAP Setup on Baremetal using Rancher. Please let me
> know if i execute below script will install all the required pieces
> or any other steps i need.
> https://wiki.onap.org/display/DW/ONAP+on+Kubernetes+on+Rancher
> 
> 
> git clone https://gerrit.onap.org/r/oom
> cd oom
> git pull https://gerrit.onap.org/r/oom refs/changes/19/32019/6
> cd install/rancher
> ./oom_rancher_setup.sh -b master -s 10.12.5.168 -e onap
>  
> 
> Thanks
> Deepak
> 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  s://www.amdocs.com/about/email-disclaimer>
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

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

Re: [onap-discuss] [APPC] - VNF Configuration using Chef adapter

[CHO, TAKAMUNE]

Hi Mahendra,

I would recommend to use R2 release code.  So that you could use CDT tool for 
self on boarding: 
http://onap.readthedocs.io/en/latest/submodules/appc.git/docs/APPC%20CDT%20Guide/APPC%20CDT%20Guide.html.
 Scott created a very nice tutorial video for CDT, you may take a look: 
https://wiki.onap.org/display/DW/Creating+the+vLoadBalancer+in+the+CDT


Appc southbound properties should be residing the same dir as appc.properties 
in appc container.

Hope that would help

Taka


From: Mahendra Raghuwanshi [mailto:mahendra.raghuwan...@amdocs.com]
Sent: Wednesday, May 23, 2018 12:16 AM
To: CHO, TAKAMUNE ; onap-discuss@lists.onap.org
Subject: RE: [APPC] - VNF Configuration using Chef adapter

Also I am working on R1. I am not able to see any appc_southbound.properties 
file in the appc container.

Thx,
Mahendra

From: Mahendra Raghuwanshi
Sent: Wednesday, May 23, 2018 9:34 AM
To: 'CHO, TAKAMUNE' >; 
onap-discuss@lists.onap.org
Subject: RE: [APPC] - VNF Configuration using Chef adapter

Hi Taka,

Thanks for your reply!!!
I went through the discussion around Ansible configuration in APPC and it 
really helps.

The doubt I have is related to the model definition for my VNF type. Where do I 
have to provide this model? What should be the format of the files? Or its just 
DB where I have to make the changes?

Thx,
Mahendra

From: CHO, TAKAMUNE [mailto:tc0...@att.com]
Sent: Tuesday, May 22, 2018 7:04 PM
To: Mahendra Raghuwanshi 
>; 
onap-discuss@lists.onap.org
Subject: RE: [APPC] - VNF Configuration using Chef adapter

Hi Mahendra,

In the past R1 release, and current R2 release, the Chef are not our primary 
goal for APPC. Hence the document for Chef  was a bit old: 
https://wiki.onap.org/display/DW/APP-C+Chef+Adapter

You also can refer Chef's DG is: 
https://gerrit.onap.org/r/gitweb?p=appc.git;a=blob;f=appc-directed-graph/appc-dgraph/provider/src/main/resources/json/APPC/APPC_Generic_ChefDG.json;h=108b18902cebf5f7019c813c6958a7c6ef39ad08;hb=refs/heads/master

The Chef Impl code is 
https://gerrit.onap.org/r/gitweb?p=appc.git;a=blob;f=appc-adapters/appc-chef-adapter/appc-chef-adapter-bundle/src/main/java/org/onap/appc/adapter/chef/impl/ChefAdapterImpl.java;h=bd367b035116151ee3573bb6885d70ade866d65b;hb=refs/heads/master

There were a couples discussions for Ansible configuration recently - that may 
help you configure Chef.

Let me know if you need more help.

Taka

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Mahendra Raghuwanshi
Sent: Monday, May 21, 2018 3:39 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [APPC] - VNF Configuration using Chef adapter

Hi,

I am looking for some help in configuring APPC to use Chef for configuring few 
of the VNFs in Amsterdam release.
I have setup the ONAP using OOM and On-boarded my VNF.

But as of now I am not able to configure my VNF using LCM as I don't have any 
idea how to configure Chef adapter and use it correctly.

Thx,
Mahendra
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