Re: [onap-discuss] Please Update Docker Manifest

[Gary Wu]

Hi Victor,

The script is at 
https://git.onap.org/integration/tree/version-manifest/src/main/scripts/update-oom-image-versions.sh.
  I expect it to be run mainly by a few people from the integration or OOM 
teams, so I didn’t send out the link earlier.  Once we get the manifest in sync 
with with HEAT and OOM, ideally we can have this triggered automatically based 
on updates to the manifest itself.

Thanks,
Gary

From: Morales, Victor [mailto:victor.mora...@intel.com]
Sent: Monday, May 07, 2018 6:35 PM
To: Gary Wu ; 'onap-discuss@lists.onap.org' 

Subject: Re: [onap-discuss] Please Update Docker Manifest

Hey Gary,

Maybe that’s me, but I couldn’t find the reference to the script that you were 
referring.  In the other hand, I’m in favor for having a “single source of 
truth” the only thing that came to my mind is about the CSV format, this can be 
limited compared with other formats.

Regards,
Victor Morales

From: 
>
 on behalf of Gary Wu >
Date: Monday, May 7, 2018 at 1:16 PM
To: "'onap-discuss@lists.onap.org'" 
>
Subject: Re: [onap-discuss] Please Update Docker Manifest

HI all,

I've just added a script that will update the OOM helm charts using the 
versions from the docker-manifest.csv.  This script assumes that the 
docker-manifest.csv contains the “definitive” versions that should be deployed 
with either OOM or HEAT.

Please take a look at the proposed helm chart changes at 
https://gerrit.onap.org/r/#/c/46451/ and verify that the changes are sane for 
your respective projects.  If anything seems wrong, please update the docker 
manifest in the integration repo to provide the right image versions.

Going forward, teams should only need to update the manifest as the "single 
source of truth", and we'll sync the OOM and HEAT docker image versions from 
there.

Also a reminder that we need all docker images to be release versions by RC2 
(May 17th).

Thanks,
Gary

_
From: Gary Wu
Sent: Thursday, May 03, 2018 7:53 PM
To: 'onap-discuss@lists.onap.org' 
>
Subject: Please Update Docker Manifest


Hi all,

It’s come to our attention that some entries in the docker manifest do not 
actually exist in nexus3.  Since we’re now past RC1, I’m turning on a 
validation to ensure that all the docker image versions specified in the 
manifest actually exist on nexus3.

While doing so, I had to change various docker image names and tags to ones 
that actually exist.  Please check the changes here:  
https://gerrit.onap.org/r/#/c/46041/3/version-manifest/src/main/resources/docker-manifest.csv
 so make sure that the new values are right for your images.

There are still quite a large number of docker images using tags containing 
“latest”, “STAGING”, or “SNAPSHOT” in the tag string.  By RC2, all docker 
images in the manifest must be release versions.  Please start releasing your 
docker images as you’re ready, and be sure to update the manifest with your 
version updates when that happens.  This is the set of versions that 
Integration will use for the purposes of deployment and use-case testing.

Thanks,
Gary


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

Re: [onap-discuss] Please Update Docker Manifest

[Morales, Victor]

Hey Gary,

Maybe that’s me, but I couldn’t find the reference to the script that you were 
referring.  In the other hand, I’m in favor for having a “single source of 
truth” the only thing that came to my mind is about the CSV format, this can be 
limited compared with other formats.

Regards,
Victor Morales

From:  on behalf of Gary Wu 

Date: Monday, May 7, 2018 at 1:16 PM
To: "'onap-discuss@lists.onap.org'" 
Subject: Re: [onap-discuss] Please Update Docker Manifest

HI all,

I've just added a script that will update the OOM helm charts using the 
versions from the docker-manifest.csv.  This script assumes that the 
docker-manifest.csv contains the “definitive” versions that should be deployed 
with either OOM or HEAT.

Please take a look at the proposed helm chart changes at 
https://gerrit.onap.org/r/#/c/46451/ and verify that the changes are sane for 
your respective projects.  If anything seems wrong, please update the docker 
manifest in the integration repo to provide the right image versions.

Going forward, teams should only need to update the manifest as the "single 
source of truth", and we'll sync the OOM and HEAT docker image versions from 
there.

Also a reminder that we need all docker images to be release versions by RC2 
(May 17th).

Thanks,
Gary

_
From: Gary Wu
Sent: Thursday, May 03, 2018 7:53 PM
To: 'onap-discuss@lists.onap.org' 
Subject: Please Update Docker Manifest


Hi all,

It’s come to our attention that some entries in the docker manifest do not 
actually exist in nexus3.  Since we’re now past RC1, I’m turning on a 
validation to ensure that all the docker image versions specified in the 
manifest actually exist on nexus3.

While doing so, I had to change various docker image names and tags to ones 
that actually exist.  Please check the changes here:  
https://gerrit.onap.org/r/#/c/46041/3/version-manifest/src/main/resources/docker-manifest.csv
 so make sure that the new values are right for your images.

There are still quite a large number of docker images using tags containing 
“latest”, “STAGING”, or “SNAPSHOT” in the tag string.  By RC2, all docker 
images in the manifest must be release versions.  Please start releasing your 
docker images as you’re ready, and be sure to update the manifest with your 
version updates when that happens.  This is the set of versions that 
Integration will use for the purposes of deployment and use-case testing.

Thanks,
Gary


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

Re: [onap-discuss] ONAP platform deployment no successful

[ANAPAN-LAVALLE, HECTOR A]

Santi,

As a follow-up to the Amsterdam deployment issue you were facing, it may be 
helpful to look into this section of the wiki which explains that multi-node 
k8s clusters need to have a master/slave setup of their NFS’s in each of the 
nodes. That solved the problem on my end.

https://wiki.onap.org/display/DW/ONAP+on+Windriver+ONAP+Developer+Cloud#ONAPonWindriverONAPDeveloperCloud-SettingupanNFSshareforMultinodeKubernetesClusters

From: Santi Rodríguez 
Sent: Monday, May 07, 2018 6:49 AM
To: ANAPAN-LAVALLE, HECTOR A 
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] ONAP platform deployment no successful

Hi Hector A,
thank you for your response.


Santiago Rodríguez García | Senior Analyst
T/ + 34 986 410 091 (ext) 227
www.optaresolutions.com
[Optare
 
Solutions]

2018-04-25 1:13 GMT+02:00 ANAPAN-LAVALLE, HECTOR A 
>:

Hi Santi,



For the Amsterdam release:



-I have come across that same error when I deployed ONAP in a multi-node/vm 
HA Kubernetes version of Rancher 
(https://rancher.com/docs/rancher/v1.6/en/kubernetes/resiliency-planes/)
 but not when the K8S cluster is hosted on a single VM only, so wondering if 
you tried doing this. One thing to make sure is to try using the latest 
supported version of docker for rancher which is 17.03.x I believe 
(https://rancher.com/docs/rancher/v1.6/en/hosts/#supported-docker-versions).

-Also, I used the README.md when installing ONAP using the OOM Amsterdam 
release (running createConfig.sh -n onap to create the namespace first, then 
running createAll.sh -n onap to create the ONAP instance)





For the Beijing release:



-While the code is not stable enough yet, there was an issue with the 
docker image registry 
(nexus3.onap.org)
 for the past few weeks but my understanding is that it has been solved.

-Also, you may want to look into having a local docker proxy that pulls the 
images from the LF docker registry to pull the images faster and more 
consistently 
(https://docs.docker.com/registry/recipes/mirror/).
 Another option is to download your own local nexus3 OSS repo in its own 
instance, and use it as a docker registry to proxy the images from 
nexus3.onap.org.



=

=

=







Hi all,



I've been trying to deploy the ONAP entire platform in my local environment

following the official documentation without the desired results:



   - First, I tried the amsterdam release installation:

  - kubectl 1.7.7

  - rancher 1.6.10

  - helm 2.3.0

  - docker 1.12

  - onap deployment using oom:

 - install/deployment/cd.sh

 - oom/kubernetes/oneclick/createAll.sh



Some of the pods are returning errors like:



Error syncing pod

Back-off restarting failed container

(combined from similar events): Error: failed to start container

"filebeat-onap-aai-model-loader": Error response from daemon:

{"*message":"invalid

header field value* \"oci runtime error: container_linux.go:247: starting

container process caused 
\\\"process_linux.go:359: container init caused

\\\"rootfs_linux.go:53: mounting

Re: [onap-discuss] [Onap-release] [ONAP Helpdesk #55152] [linuxfoundation.org #55152] RE: [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April

[Gary Wu via RT]

I've just added a script that will update the OOM helm charts using the 
versions from the docker-manifest.csv.  Going forward, teams should only need 
to update the manifest as the "single source of truth", and we'll sync the OOM 
and HEAT docker image versions from there.

Thanks,
Gary

-Original Message-
From: onap-release-boun...@lists.onap.org 
[mailto:onap-release-boun...@lists.onap.org] On Behalf Of dt5...@att.com via RT
Sent: Monday, May 07, 2018 11:10 AM
To: frank.obr...@amdocs.com
Cc: onap-discuss@lists.onap.org; onap-rele...@lists.onap.org
Subject: Re: [Onap-release] [onap-discuss] [ONAP Helpdesk #55152] 
[linuxfoundation.org #55152] RE: [CCSDK] ccsdk-dgbuilder-image had no 
0.2.1-SNAPSHOT until 20 April

Michael,

I believe the Heat environment is using the version manifests.  So I think we 
only have 2 places to update now - which is still one too many, but such is 
life.   The good news is there's no changes between 0.2.1-SNAPSHOT and 
0.2.2-SNAPSHOT of dgbuilder, so you're not missing any bug fixes but I'll 
certainly get that updated in OOM.


Dan

-- 
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO
 
Please go to  D2 ECOMP Release Planning Wiki 
 for D2 
ECOMP Project In-take, 2016 Release Planning, Change Management, and find key 
Release Planning Contact Information.
 
On 5/7/18, 1:58 PM, "onap-discuss-boun...@lists.onap.org on behalf of Michael 
O'Brien via RT"  wrote:

Dan,
   Hi, I am using ONAP out of the box – no changes.
   The image changes anyone makes to HEAT, OOM need to also be made to the 
other side in order for both ONAP deployment options to be in sync.
   The image tag for OOM for SDNC and APPC were not updated in sync with 
the HEAT and manifest change.
   A note for all PTS’s: any change to any of the 3 configuration places 
(until we have automated yaml generation) – must be done in sync in all three 
places
  The manifest
  HEAT
  OOM

   CCSDK and any other common charts are a bit of a special case – as 
either PTL needs to make the change for the other project – when using cross 
project charts like common/dgbuilder.


https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_46423_=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=g5iDyAsou22Nfxj8QZL5EBVYg1eUmhCNIR0X6t6IZFY=7y2q8-lYULDtlC81W7JOw4S1piwQSK_0uJQlMuvAKEs=
 
The above change is being tested on a live deployment – ETA 90 min before 
it can be merged.


The secondary on this is – this issue only came up because the LF deleted 
the older image – without the LF’s periodic purge – SDNC and APPC would have 
continued working with the old images for a while

Thank you
/michael

From: TIMONEY, DAN [mailto:dt5...@att.com]
Sent: Monday, May 7, 2018 9:32 AM
To: Michael O'Brien ; 
'onap-rele...@lists.onap.org' ; 
'onap-discuss@lists.onap.org' 
Cc: 'helpd...@onap.org' 
Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 
0.2.1-SNAPSHOT until 20 April

All,

You shouldn’t really be using snapshot versions of the CCSDK docker images. 
 You should be using version 0.2-STAGING-latest for CCSDK (and 
1.3-STAGING-latest for SDN-C)

I noticed last week that the docker version manifest incorrectly specified 
snapshot versions for the CCSDK docker images, so I fixed that.   Sorry if that 
caused any confusion.

Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.

From: 
>
 on behalf of "OBRIEN, FRANK MICHAEL" 
>
Date: Monday, May 7, 2018 at 7:52 AM
To: "'onap-rele...@lists.onap.org'" 
>, onap-discuss 
>
Cc: "'helpd...@onap.org'" >
Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 
0.2.1-SNAPSHOT until 20 April

Team,
   The image was deleted again – looks like as James M. has mentioned – the 
rule for nexus3 deletion should be “delete 2 week old images – unless there has 
been no build in the past 2 weeks” – to keep at least 1 snapshot around

Re: [onap-discuss] [Onap-release] [ONAP Helpdesk #55152] [linuxfoundation.org #55152] RE: [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April

[Gary Wu]

I've just added a script that will update the OOM helm charts using the 
versions from the docker-manifest.csv.  Going forward, teams should only need 
to update the manifest as the "single source of truth", and we'll sync the OOM 
and HEAT docker image versions from there.

Thanks,
Gary

-Original Message-
From: onap-release-boun...@lists.onap.org 
[mailto:onap-release-boun...@lists.onap.org] On Behalf Of dt5...@att.com via RT
Sent: Monday, May 07, 2018 11:10 AM
To: frank.obr...@amdocs.com
Cc: onap-discuss@lists.onap.org; onap-rele...@lists.onap.org
Subject: Re: [Onap-release] [onap-discuss] [ONAP Helpdesk #55152] 
[linuxfoundation.org #55152] RE: [CCSDK] ccsdk-dgbuilder-image had no 
0.2.1-SNAPSHOT until 20 April

Michael,

I believe the Heat environment is using the version manifests.  So I think we 
only have 2 places to update now - which is still one too many, but such is 
life.   The good news is there's no changes between 0.2.1-SNAPSHOT and 
0.2.2-SNAPSHOT of dgbuilder, so you're not missing any bug fixes but I'll 
certainly get that updated in OOM.


Dan

-- 
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO
 
Please go to  D2 ECOMP Release Planning Wiki 
 for D2 
ECOMP Project In-take, 2016 Release Planning, Change Management, and find key 
Release Planning Contact Information.
 
On 5/7/18, 1:58 PM, "onap-discuss-boun...@lists.onap.org on behalf of Michael 
O'Brien via RT"  wrote:

Dan,
   Hi, I am using ONAP out of the box – no changes.
   The image changes anyone makes to HEAT, OOM need to also be made to the 
other side in order for both ONAP deployment options to be in sync.
   The image tag for OOM for SDNC and APPC were not updated in sync with 
the HEAT and manifest change.
   A note for all PTS’s: any change to any of the 3 configuration places 
(until we have automated yaml generation) – must be done in sync in all three 
places
  The manifest
  HEAT
  OOM

   CCSDK and any other common charts are a bit of a special case – as 
either PTL needs to make the change for the other project – when using cross 
project charts like common/dgbuilder.


https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_46423_=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=g5iDyAsou22Nfxj8QZL5EBVYg1eUmhCNIR0X6t6IZFY=7y2q8-lYULDtlC81W7JOw4S1piwQSK_0uJQlMuvAKEs=
 
The above change is being tested on a live deployment – ETA 90 min before 
it can be merged.


The secondary on this is – this issue only came up because the LF deleted 
the older image – without the LF’s periodic purge – SDNC and APPC would have 
continued working with the old images for a while

Thank you
/michael

From: TIMONEY, DAN [mailto:dt5...@att.com]
Sent: Monday, May 7, 2018 9:32 AM
To: Michael O'Brien ; 
'onap-rele...@lists.onap.org' ; 
'onap-discuss@lists.onap.org' 
Cc: 'helpd...@onap.org' 
Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 
0.2.1-SNAPSHOT until 20 April

All,

You shouldn’t really be using snapshot versions of the CCSDK docker images. 
 You should be using version 0.2-STAGING-latest for CCSDK (and 
1.3-STAGING-latest for SDN-C)

I noticed last week that the docker version manifest incorrectly specified 
snapshot versions for the CCSDK docker images, so I fixed that.   Sorry if that 
caused any confusion.

Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.

From: 
>
 on behalf of "OBRIEN, FRANK MICHAEL" 
>
Date: Monday, May 7, 2018 at 7:52 AM
To: "'onap-rele...@lists.onap.org'" 
>, onap-discuss 
>
Cc: "'helpd...@onap.org'" >
Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 
0.2.1-SNAPSHOT until 20 April

Team,
   The image was deleted again – looks like as James M. has mentioned – the 
rule for nexus3 deletion should be “delete 2 week old images – unless there has 
been no build in the past 2 weeks” – to keep at least 1 snapshot around

Re: [onap-discuss] ONAP installation issue with Azure VM

[Mohan L]

Hi Michael,


Mohan,
>
>Hi, pending state for your kubernetes system means that your server is
> not reachable from your host (same machine in this case)
>
>If you don’t wish to extend your system into a clustered system you
> should be able to use the 172.xxx ip for host registration.
>
>The script inserts a record for the hostname into your /etc/hosts and
> by default uses this to register rancher/kubernetes.
>
>
>
> Went through your paste – your issue may be the choice of hostname – try
> something different without underscores and capitals
>

>
> INFO: ENV: CATTLE_URL=http://Public_IP:8880/v1
>
> INFO: ENV: DETECTED_CATTLE_AGENT_IP=Public_IP
>

The Public_IP address is my VM public IP address. I just replaced
​10.xx.xx.xx to Public_IP for security reason.



>
>
> You may docker delete and docker rm your server/client container and rerun
> the oom rancher install with a real/routable IP as well.
>
> Or go into the admin section of rancher and change the server IP/host
>
>
>
> Also I am a little suspect of how this script was run – if you ran it as
> part of template you would not see your-user
>
> sudo usermod -aG docker your-user
>
>
>
>
​The ARM template runs entrypoint at the end. I removed it and created VM
using ARM template then I am running oom_rancher_setup.sh on the VM using:

# ./oom_rancher_setup.sh -b master -s xx.xx.xx.xx -e onap

Here is the output of # kubectl describe pod kube-dns-5d7b4487c9-dt6bf
--namespace=kube-system

http://paste.openstack.org/show/720514/

All the pod shows no nodes available to schedule pods like below. any help?

Events:
  Type ReasonAge From   Message
   --   ---
  Warning  FailedScheduling  4m (x140 over 44m)  default-scheduler  no
nodes available to schedule pods


no nodes available to schedule pods




>
> *From:* onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-bounces@
> lists.onap.org] *On Behalf Of *Mohan L
> *Sent:* Monday, May 7, 2018 2:09 PM
> *To:* onap-discuss@lists.onap.org
> *Subject:* [onap-discuss] ONAP installation issue with Azure VM
>
>
>
> Hi All,
>
>
>
> I created a Azure VM with 32vCPU and 128 GB RAM using ARM template
> attached in OOM-711. I ran oom_rancher_setup.sh script which is attached in
> OOM-715 and the script execution went well with out any error. But all the
> pods are pending state for long time.
>
>
>
> Here is the complete oom_rancher_setup.sh: http://
> paste.openstack.org/show/720508/
>
>
>
>
>
> Any help will be really appreciated.
>
>
>
> # kubectl get pods --all-namespaces
>
> NAMESPACE NAME   READY STATUS
> RESTARTS   AGE
>
> kube-system   heapster-76b8cd7b5-4xkfg   0/1   Pending   0
>   1h
>
> kube-system   kube-dns-5d7b4487c9-dt6bf  0/3   Pending   0
>   1h
>
> kube-system   kubernetes-dashboard-f9577fffd-fxtsz   0/1   Pending   0
>   1h
>
> kube-system   monitoring-grafana-997796fcf-gzj65 0/1   Pending   0
>   1h
>
> kube-system   monitoring-influxdb-56fdcd96b-j5hx70/1   Pending   0
>   1h
>
> kube-system   tiller-deploy-54bcc55dd5-m6tpg 0/1   Pending   0
>   1h
>
>
>
>
>
>
>
> # kubectl cluster-info
>
> Kubernetes master is running at 
> https://Public_IP:8880/r/projects/1a7/kubernetes:6443
>
> Heapster is running at 
> https://Public_IP:8880/r/projects/1a7/kubernetes:6443/api/v1/namespaces/kube-system/services/heapster/proxy
>
> KubeDNS is running at 
> https://Public_IP:8880/r/projects/1a7/kubernetes:6443/api/v1/namespaces/kube-system/services/kube-dns/proxy
>
> kubernetes-dashboard is running at 
> https://Public_IP:8880/r/projects/1a7/kubernetes:6443/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy
>
> monitoring-grafana is running at 
> https://Public_IP:8880/r/projects/1a7/kubernetes:6443/api/v1/namespaces/kube-system/services/monitoring-grafana/proxy
>
> monitoring-influxdb is running at 
> https://Public_IP:8880/r/projects/1a7/kubernetes:6443/api/v1/namespaces/kube-system/services/monitoring-influxdb/proxy
>
> tiller-deploy is running at 
> https://Public_IP:8880/r/projects/1a7/kubernetes:6443/api/v1/namespaces/kube-system/services/tiller-deploy/proxy
>
>
>
>
>
> --
>
> Thanks & Regards
>
> Mobile: 9444955058
>
> E-Mail: l.mohan...@gmail.com | thefossg...@gmail.com
>
> IRC: neophy
>
> Blog : http://lmohanphy.livejournal.com/
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> you may review at https://www.amdocs.com/about/email-disclaimer
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Debugging Portal/Music java code in container

[William Kurkian]

I have an issue logging into the Portal in my ONAP deployment. I have
described the issue here: https://jira.onap.org/browse/MUSIC-75.

Basically there is a null pointer exception. How can I setup a debugger to
see what is happening here? Is there a resource on how to do this ?

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

Re: [onap-discuss] [ONAP Helpdesk #55152] [linuxfoundation.org #55152] RE: [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April

[TIMONEY, DAN]

Michael,

I believe the Heat environment is using the version manifests.  So I think we 
only have 2 places to update now - which is still one too many, but such is 
life.   The good news is there's no changes between 0.2.1-SNAPSHOT and 
0.2.2-SNAPSHOT of dgbuilder, so you're not missing any bug fixes but I'll 
certainly get that updated in OOM.


Dan

-- 
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO
 
Please go to  D2 ECOMP Release Planning Wiki 
 for D2 
ECOMP Project In-take, 2016 Release Planning, Change Management, and find key 
Release Planning Contact Information.
 
On 5/7/18, 1:58 PM, "onap-discuss-boun...@lists.onap.org on behalf of Michael 
O'Brien via RT"  wrote:

Dan,
   Hi, I am using ONAP out of the box – no changes.
   The image changes anyone makes to HEAT, OOM need to also be made to the 
other side in order for both ONAP deployment options to be in sync.
   The image tag for OOM for SDNC and APPC were not updated in sync with 
the HEAT and manifest change.
   A note for all PTS’s: any change to any of the 3 configuration places 
(until we have automated yaml generation) – must be done in sync in all three 
places
  The manifest
  HEAT
  OOM

   CCSDK and any other common charts are a bit of a special case – as 
either PTL needs to make the change for the other project – when using cross 
project charts like common/dgbuilder.


https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_46423_=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=g5iDyAsou22Nfxj8QZL5EBVYg1eUmhCNIR0X6t6IZFY=7y2q8-lYULDtlC81W7JOw4S1piwQSK_0uJQlMuvAKEs=
 
The above change is being tested on a live deployment – ETA 90 min before 
it can be merged.


The secondary on this is – this issue only came up because the LF deleted 
the older image – without the LF’s periodic purge – SDNC and APPC would have 
continued working with the old images for a while

Thank you
/michael

From: TIMONEY, DAN [mailto:dt5...@att.com]
Sent: Monday, May 7, 2018 9:32 AM
To: Michael O'Brien ; 
'onap-rele...@lists.onap.org' ; 
'onap-discuss@lists.onap.org' 
Cc: 'helpd...@onap.org' 
Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 
0.2.1-SNAPSHOT until 20 April

All,

You shouldn’t really be using snapshot versions of the CCSDK docker images. 
 You should be using version 0.2-STAGING-latest for CCSDK (and 
1.3-STAGING-latest for SDN-C)

I noticed last week that the docker version manifest incorrectly specified 
snapshot versions for the CCSDK docker images, so I fixed that.   Sorry if that 
caused any confusion.

Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.

From: 
>
 on behalf of "OBRIEN, FRANK MICHAEL" 
>
Date: Monday, May 7, 2018 at 7:52 AM
To: "'onap-rele...@lists.onap.org'" 
>, onap-discuss 
>
Cc: "'helpd...@onap.org'" >
Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 
0.2.1-SNAPSHOT until 20 April

Team,
   The image was deleted again – looks like as James M. has mentioned – the 
rule for nexus3 deletion should be “delete 2 week old images – unless there has 
been no build in the past 2 weeks” – to keep at least 1 snapshot around


https://urldefense.proofpoint.com/v2/url?u=http-3A__jenkins.onap.info_job_oom-2Dcd-2Dmaster_2880_console=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=g5iDyAsou22Nfxj8QZL5EBVYg1eUmhCNIR0X6t6IZFY=6IunU8CqwfJ9AgiX3Vp12sVz4JFUbpbRvquUfipgAjw=
 


10:54:55 onap  onap-appc-dgbuilder-6bbd4dbdcd-xwq7k 
 0/1   ImagePullBackOff   0  1h10.42.75.136
ip-10-0-0-136.us-east-2.compute.internal


10:54:55 onap  onap-sdnc-dgbuilder-76589b66b6-bwpk2 
 0/1   ImagePullBackOff   0   

[onap-discuss] ONAP installation issue with Azure VM

[Mohan L]

Hi All,

I created a Azure VM with 32vCPU and 128 GB RAM using ARM template attached
in OOM-711. I ran oom_rancher_setup.sh script which is attached in OOM-715
and the script execution went well with out any error. But all the pods are
pending state for long time.

Here is the complete oom_rancher_setup.sh:
http://paste.openstack.org/show/720508/


Any help will be really appreciated.

# kubectl get pods --all-namespaces
NAMESPACE NAME   READY STATUS
  RESTARTS   AGE
kube-system   heapster-76b8cd7b5-4xkfg   0/1   Pending
  0  1h
kube-system   kube-dns-5d7b4487c9-dt6bf  0/3   Pending
  0  1h
kube-system   kubernetes-dashboard-f9577fffd-fxtsz   0/1   Pending
  0  1h
kube-system   monitoring-grafana-997796fcf-gzj65 0/1   Pending
  0  1h
kube-system   monitoring-influxdb-56fdcd96b-j5hx70/1   Pending
  0  1h
kube-system   tiller-deploy-54bcc55dd5-m6tpg 0/1   Pending
  0  1h



# kubectl cluster-info
Kubernetes master is running at
https://Public_IP:8880/r/projects/1a7/kubernetes:6443
Heapster is running at
https://Public_IP:8880/r/projects/1a7/kubernetes:6443/api/v1/namespaces/kube-system/services/heapster/proxy
KubeDNS is running at
https://Public_IP:8880/r/projects/1a7/kubernetes:6443/api/v1/namespaces/kube-system/services/kube-dns/proxy
kubernetes-dashboard is running at
https://Public_IP:8880/r/projects/1a7/kubernetes:6443/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy
monitoring-grafana is running at
https://Public_IP:8880/r/projects/1a7/kubernetes:6443/api/v1/namespaces/kube-system/services/monitoring-grafana/proxy
monitoring-influxdb is running at
https://Public_IP:8880/r/projects/1a7/kubernetes:6443/api/v1/namespaces/kube-system/services/monitoring-influxdb/proxy
tiller-deploy is running at
https://Public_IP:8880/r/projects/1a7/kubernetes:6443/api/v1/namespaces/kube-system/services/tiller-deploy/proxy



--
Thanks & Regards
Mobile: 9444955058
E-Mail: l.mohan...@gmail.com | thefossg...@gmail.com
IRC: neophy
Blog : http://lmohanphy.livejournal.com/
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [CCSDK] docker image sync between HEAT and OOM deployments

[Michael O'Brien]

Gildas,
  Just an fyi for the TSC – there are several issues here (3)
  Docker sync between the 2 ONAP versions needs to be enforced – until we have 
the manifest completely automated with heat and OOM extracts.

  We are sensitive to the state on nexus3 deleting/retaining old images in 
order to function – in this case we should not have been working when the heat 
side was done  -  OOM continued to work because the older image stayed up for a 
while.

   The 3rd is – who is responsible for common project changes – in this case 
CCSDK should have updated SDNC and APPC – or APPC and SDNC need to be aware of 
CCSDK changes for each other.
  /michael

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Michael O'Brien
Sent: Monday, May 7, 2018 1:58 PM
To: TIMONEY, DAN ; 'onap-rele...@lists.onap.org' 
; 'onap-discuss@lists.onap.org' 

Cc: 'helpd...@onap.org' 
Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT 
until 20 April

Dan,
   Hi, I am using ONAP out of the box – no changes.
   The image changes anyone makes to HEAT, OOM need to also be made to the 
other side in order for both ONAP deployment options to be in sync.
   The image tag for OOM for SDNC and APPC were not updated in sync with the 
HEAT and manifest change.
   A note for all PTS’s: any change to any of the 3 configuration places (until 
we have automated yaml generation) – must be done in sync in all three places
  The manifest
  HEAT
  OOM

   CCSDK and any other common charts are a bit of a special case – as either 
PTL needs to make the change for the other project – when using cross project 
charts like common/dgbuilder.

https://gerrit.onap.org/r/#/c/46423/
The above change is being tested on a live deployment – ETA 90 min before it 
can be merged.


The secondary on this is – this issue only came up because the LF deleted the 
older image – without the LF’s periodic purge – SDNC and APPC would have 
continued working with the old images for a while

Thank you
/michael

From: TIMONEY, DAN [mailto:dt5...@att.com]
Sent: Monday, May 7, 2018 9:32 AM
To: Michael O'Brien >; 
'onap-rele...@lists.onap.org' 
>; 
'onap-discuss@lists.onap.org' 
>
Cc: 'helpd...@onap.org' >
Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT 
until 20 April

All,

You shouldn’t really be using snapshot versions of the CCSDK docker images.  
You should be using version 0.2-STAGING-latest for CCSDK (and 
1.3-STAGING-latest for SDN-C)

I noticed last week that the docker version manifest incorrectly specified 
snapshot versions for the CCSDK docker images, so I fixed that.   Sorry if that 
caused any confusion.

Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.

From: 
>
 on behalf of "OBRIEN, FRANK MICHAEL" 
>
Date: Monday, May 7, 2018 at 7:52 AM
To: "'onap-rele...@lists.onap.org'" 
>, onap-discuss 
>
Cc: "'helpd...@onap.org'" >
Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT 
until 20 April

Team,
   The image was deleted again – looks like as James M. has mentioned – the 
rule for nexus3 deletion should be “delete 2 week old images – unless there has 
been no build in the past 2 weeks” – to keep at least 1 snapshot around

http://jenkins.onap.info/job/oom-cd-master/2880/console

10:54:55 onap  onap-appc-dgbuilder-6bbd4dbdcd-xwq7k 
 0/1   ImagePullBackOff   0  1h10.42.75.136
ip-10-0-0-136.us-east-2.compute.internal


10:54:55 onap  onap-sdnc-dgbuilder-76589b66b6-bwpk2 
 0/1   ImagePullBackOff   0  1h10.42.68.150
ip-10-0-0-136.us-east-2.compute.internal


Warning Failed 5m (x14 over 2h) kubelet, 
ip-10-0-0-136.us-east-2.compute.internal Failed to pull image 

Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April

[Michael O'Brien]

Dan,
   Hi, I am using ONAP out of the box – no changes.
   The image changes anyone makes to HEAT, OOM need to also be made to the 
other side in order for both ONAP deployment options to be in sync.
   The image tag for OOM for SDNC and APPC were not updated in sync with the 
HEAT and manifest change.
   A note for all PTS’s: any change to any of the 3 configuration places (until 
we have automated yaml generation) – must be done in sync in all three places
  The manifest
  HEAT
  OOM

   CCSDK and any other common charts are a bit of a special case – as either 
PTL needs to make the change for the other project – when using cross project 
charts like common/dgbuilder.

https://gerrit.onap.org/r/#/c/46423/
The above change is being tested on a live deployment – ETA 90 min before it 
can be merged.


The secondary on this is – this issue only came up because the LF deleted the 
older image – without the LF’s periodic purge – SDNC and APPC would have 
continued working with the old images for a while

Thank you
/michael

From: TIMONEY, DAN [mailto:dt5...@att.com]
Sent: Monday, May 7, 2018 9:32 AM
To: Michael O'Brien ; 'onap-rele...@lists.onap.org' 
; 'onap-discuss@lists.onap.org' 

Cc: 'helpd...@onap.org' 
Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT 
until 20 April

All,

You shouldn’t really be using snapshot versions of the CCSDK docker images.  
You should be using version 0.2-STAGING-latest for CCSDK (and 
1.3-STAGING-latest for SDN-C)

I noticed last week that the docker version manifest incorrectly specified 
snapshot versions for the CCSDK docker images, so I fixed that.   Sorry if that 
caused any confusion.

Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.

From: 
>
 on behalf of "OBRIEN, FRANK MICHAEL" 
>
Date: Monday, May 7, 2018 at 7:52 AM
To: "'onap-rele...@lists.onap.org'" 
>, onap-discuss 
>
Cc: "'helpd...@onap.org'" >
Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT 
until 20 April

Team,
   The image was deleted again – looks like as James M. has mentioned – the 
rule for nexus3 deletion should be “delete 2 week old images – unless there has 
been no build in the past 2 weeks” – to keep at least 1 snapshot around

http://jenkins.onap.info/job/oom-cd-master/2880/console

10:54:55 onap  onap-appc-dgbuilder-6bbd4dbdcd-xwq7k 
 0/1   ImagePullBackOff   0  1h10.42.75.136
ip-10-0-0-136.us-east-2.compute.internal


10:54:55 onap  onap-sdnc-dgbuilder-76589b66b6-bwpk2 
 0/1   ImagePullBackOff   0  1h10.42.68.150
ip-10-0-0-136.us-east-2.compute.internal


Warning Failed 5m (x14 over 2h) kubelet, 
ip-10-0-0-136.us-east-2.compute.internal Failed to pull image 
"nexus3.onap.org:10001/onap/ccsdk-dgbuilder-image:0.2.1-SNAPSHOT": rpc error: 
code = Unknown desc = Tag 0.2.1-SNAPSHOT not found in repository 
nexus3.onap.org:10001/onap/ccsdk-dgbuilder-image

/michael

From: Michael O'Brien
Sent: Tuesday, April 24, 2018 5:19 PM
To: onap-rele...@lists.onap.org; 
onap-discuss@lists.onap.org
Cc: helpd...@onap.org
Subject: [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April

LF,
  Just would like to understand what happened to this image that broke SDNC and 
APPC for a couple days

https://jira.onap.org/browse/SDNC-285
https://jira.onap.org/browse/APPC-856

  From the logs it looks like the SNAPSHOT image was returned 4 days ago – 
before the 20th of 

[onap-discuss] [ONAP Helpdesk #55152] [linuxfoundation.org #55152] RE: [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April

[Michael O'Brien via RT]

Dan,
   Hi, I am using ONAP out of the box – no changes.
   The image changes anyone makes to HEAT, OOM need to also be made to the 
other side in order for both ONAP deployment options to be in sync.
   The image tag for OOM for SDNC and APPC were not updated in sync with the 
HEAT and manifest change.
   A note for all PTS’s: any change to any of the 3 configuration places (until 
we have automated yaml generation) – must be done in sync in all three places
  The manifest
  HEAT
  OOM

   CCSDK and any other common charts are a bit of a special case – as either 
PTL needs to make the change for the other project – when using cross project 
charts like common/dgbuilder.

https://gerrit.onap.org/r/#/c/46423/
The above change is being tested on a live deployment – ETA 90 min before it 
can be merged.


The secondary on this is – this issue only came up because the LF deleted the 
older image – without the LF’s periodic purge – SDNC and APPC would have 
continued working with the old images for a while

Thank you
/michael

From: TIMONEY, DAN [mailto:dt5...@att.com]
Sent: Monday, May 7, 2018 9:32 AM
To: Michael O'Brien ; 'onap-rele...@lists.onap.org' 
; 'onap-discuss@lists.onap.org' 

Cc: 'helpd...@onap.org' 
Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT 
until 20 April

All,

You shouldn’t really be using snapshot versions of the CCSDK docker images.  
You should be using version 0.2-STAGING-latest for CCSDK (and 
1.3-STAGING-latest for SDN-C)

I noticed last week that the docker version manifest incorrectly specified 
snapshot versions for the CCSDK docker images, so I fixed that.   Sorry if that 
caused any confusion.

Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.

From: 
>
 on behalf of "OBRIEN, FRANK MICHAEL" 
>
Date: Monday, May 7, 2018 at 7:52 AM
To: "'onap-rele...@lists.onap.org'" 
>, onap-discuss 
>
Cc: "'helpd...@onap.org'" >
Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT 
until 20 April

Team,
   The image was deleted again – looks like as James M. has mentioned – the 
rule for nexus3 deletion should be “delete 2 week old images – unless there has 
been no build in the past 2 weeks” – to keep at least 1 snapshot around

http://jenkins.onap.info/job/oom-cd-master/2880/console

10:54:55 onap  onap-appc-dgbuilder-6bbd4dbdcd-xwq7k 
 0/1   ImagePullBackOff   0  1h10.42.75.136
ip-10-0-0-136.us-east-2.compute.internal


10:54:55 onap  onap-sdnc-dgbuilder-76589b66b6-bwpk2 
 0/1   ImagePullBackOff   0  1h10.42.68.150
ip-10-0-0-136.us-east-2.compute.internal


Warning Failed 5m (x14 over 2h) kubelet, 
ip-10-0-0-136.us-east-2.compute.internal Failed to pull image 
"nexus3.onap.org:10001/onap/ccsdk-dgbuilder-image:0.2.1-SNAPSHOT": rpc error: 
code = Unknown desc = Tag 0.2.1-SNAPSHOT not found in repository 
nexus3.onap.org:10001/onap/ccsdk-dgbuilder-image

/michael

From: Michael O'Brien
Sent: Tuesday, April 24, 2018 5:19 PM
To: onap-rele...@lists.onap.org; 
onap-discuss@lists.onap.org
Cc: helpd...@onap.org
Subject: [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April

LF,
  Just would like to understand what happened to this image that broke SDNC and 
APPC for a couple days

https://jira.onap.org/browse/SDNC-285
https://jira.onap.org/browse/APPC-856

  From the logs it looks like the SNAPSHOT image was returned 4 days ago – 
before the 20th of 

Re: [onap-discuss] [ARCH] Request scope change review: Logging specification changes for Casablanca

[Christopher Donley (Chris)]

Michael,

I put you down for a 10-minute slot.

Chris

From: Michael O'Brien >
Date: Monday, May 7, 2018 at 7:12 AM
To: "'onap-discuss@lists.onap.org'" 
>
Cc: Chris Donley 
>
Subject: [ARCH] Request scope change review: Logging specification changes for 
Casablanca

Chris,
   Hi, the logging team has been meeting for about 5 weeks finalizing the 
logging specification proposed for Casablanca – we would like to pass these 
adjustments by the architecture subcommittee and the community.
https://wiki.onap.org/pages/viewpage.action?pageId=28378955


   We would like a couple meetings if possible – I would expect 5-10 min.

  1.  Heads up review of the spec and the diff  from Beijing - the MDC and 
Marker changes and proposed EPICs for Casablanca – would like to get this up 
for discussion earlier.
  2.  Demo: When we have some concrete running demo code finished and have 
prioritized/sized and agreed on the Casablanca epics – we could do another 
review the week after if possible. Discuss impact to teams, working with teams 
to implement, staged migration…


Team, Luke Parker, Shishir Thakore, Sanjay Agraharam, Neal Chatterley, Dave 
Williamson, Lee Bresleau, Xuan Liu, Horace Ip, Bob Ferro, David Bainbridge, 
Jimmy Forsyth.

   Thank you
/michael


This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] ONAP development setup

[Roger Maitland]

Hi Abhay,

onap.readthedocs.io is the official location for ONAP documentation.  When 
you’ll go there you’ll see a Platform 
Operations
 section with guides to help you setup a K8s environment – the OOM Cloud Setup 
Guide
 - (on OpenStack if you like) and how to deploy and manage ONAP - the OOM User 
Guide.
 OOM installs ONAP on a K8s cluster which, if you’re interested in just a 
partial deployment, could still be a single node. You’ll need at least two 
nodes (VMs) with 128 GB (i.e 2x64GB) to deploy all of ONAP.

Good luck.

Cheers,
Roger

From:  on behalf of abhay narayan katare 

Date: Monday, May 7, 2018 at 11:49 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] ONAP development setup


Hi,



I am new to the ONAP Technology and want to deploy full ONAP setup. Through 
different channels i came to know for full setup i need to have at least 128 GB 
RAM available. Some of my doubts are listed below. please help me here.



  1.  OOM install ONAP as  all-in-one means all components in a single server ?
  2.  if OOM can be used to install ONAP as a distributed system , what could 
be the min configuration of each server ?
  3.  Can i install using K8s or currently we have only Openstack options 
available.


Regards

Abhay
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

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

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

[onap-discuss] ONAP development setup

[abhay narayan katare]

Hi,


I am new to the ONAP Technology and want to deploy full ONAP setup. Through 
different channels i came to know for full setup i need to have at least 128 GB 
RAM available. Some of my doubts are listed below. please help me here.


  1.  OOM install ONAP as  all-in-one means all components in a single server ?
  2.  if OOM can be used to install ONAP as a distributed system , what could 
be the min configuration of each server ?
  3.  Can i install using K8s or currently we have only Openstack options 
available.


Regards

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

Re: [onap-discuss] UUI/VID Discussion

[Sonsino, Ofir]

Hi Tao,

Carrier Grade means S3P.
Testing environment is another VID feature allows to create isolated tenant for 
testing purposes.

Can you schedule another meeting? if possible tomorrow 18:00 your time (13:00 
our time)

Thanks,
Ofir

From: shentao [mailto:shen...@chinamobile.com]
Sent: Tuesday, May 01, 2018 10:27 AM
To: Nachmias, Lior ; Lefevre, Catherine 
; Sonsino, Ofir ; 'Lingli Deng' 
; 'onap-discuss' 
Cc: Lefevre, Catherine 
Subject: 答复: UUI/VID Discussion

Hi, Lior

I’ve confirmed attachment and want to clarify current status.
UUI is supporting change management function (we call it upgrade) and S3P.
And I confirmed VFC team that UUI can support VCPE/VDNS/VFW in R2.
Could you tell me what “Carrier Grade” and “Testing environment” mean.
Or we can discuss more at the next meeting next week. (we are in national 
holiday this week)

Best regards,
Tao


发件人: Nachmias, Lior [mailto:ln6...@intl.att.com]
发送时间: 2018年4月24日 16:34
收件人: shentao; Lefevre, Catherine; Sonsino, Ofir; Lingli Deng; onap-discuss
抄送: Lefevre, Catherine
主题: RE: UUI/VID Discussion

Good day,

We (UUI and VID project teams) had a call this morning to discuss how we can 
define a new project that will combine VID/UUI current functionalities, in 
order to optimize the effort by combining our team members.

Presentation and meeting notes are attached.

Thanks,
Lior Nachmias


AT Network Application Development ・ NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
・・・
Office: +972 (3) 9767757

-Original Appointment-
From: shentao [mailto:shen...@chinamobile.com]
Sent: Monday, April 23, 2018 5:57 AM
To: shentao; Lefevre, Catherine; Sonsino, Ofir; Nachmias, Lior; Lingli Deng
Subject: UUI/VID Discussion
When: Tuesday, April 24, 2018 9:30 AM-10:30 AM (UTC+02:00) Athens, Bucharest.
Where: 
https://zoom.us/j/651540147


时间: 2018年4月24日星期二 14:30-15:30(UTC+08:00) 北京，重庆，香港特别行政区，乌鲁木齐。
地点: 
https://zoom.us/j/651540147

*~*~*~*~*~*~*~*~*~*

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

Re: [onap-discuss] OOM Beijing HW requirements

[Roger Maitland]

Hi Michal,

The limit of 110 pods applies per node so if you add another node (or two) to 
your cluster you’ll avoid this problem. We’ve had problems in the past with 
multi-node configurations but that seems to be behind us.  I’ll put a note in 
the documentation – thanks for reporting the problem.

Cheers,
Roger

From:  on behalf of Michal Ptacek 

Reply-To: "m.pta...@partner.samsung.com" 
Date: Friday, May 4, 2018 at 11:08 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] OOM Beijing HW requirements




Hi all,



I am trying to deploy latest ONAP (Beijing) using OOM (master branch) and I 
found some challenges using suggested HW resources for all-in-one (rancher 
server + k8s host on single node) deployment of ONAP:



HW resources:
·24 VCPU
· 128G RAM
· 500G disc space
· rhel7.4 os
· rancher 1.6.14
· kubernetes 1.8.10
· helm 2.8.2
· kubectl 1.8.12
· docker 17.03-ce



Problem:

some random pods are unable to spawn and are on "Pending" state with error "No 
nodes are available that match all of the predicates: Insufficient pods (1).“



Analyzis:

it seems that mine server can allocate max. 110 pods, which I found from 
"kubectl describe nodes" output

...

Allocatable:

cpu: 24

memory:  102861656Ki

pods:110

...

full ONAP deployment with all components enabled might be 120+ pods but I did 
not get even that 110 running,

maybe some race-condition for latest pods. If I disable 5+ components in 
onap/values.yaml, it will fit into that server but then it seems that "Minimum 
Hardware Configuration" described in

http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_cloud_setup_guide.html

is wrong (120GB RAM, 160G disc, 16vCPU)



or is there any hint how to increase that maximum number of allocatable pods ?



thanks,

Michal

















 [cid:20180504073931_0@eucms1p]

[http://ext.w1.samsung.net/mail/ext/v1/external/status/update?userid=m.ptacek=bWFpbElEPTIwMTgwNTA0MDczOTMxZXVjbXMxcDM0NjgwOTJiMDllYWUzZTA4NmNjZWQ2NzgwOTM3OTE0ZiZyZWNpcGllbnRBZGRyZXNzPW9uYXAtZGlzY3Vzc0BsaXN0cy5vbmFwLm9yZw__]
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

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

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

[onap-discuss] [ARCH] Request scope change review: Logging specification changes for Casablanca

[Michael O'Brien]

Chris,
   Hi, the logging team has been meeting for about 5 weeks finalizing the 
logging specification proposed for Casablanca - we would like to pass these 
adjustments by the architecture subcommittee and the community.
https://wiki.onap.org/pages/viewpage.action?pageId=28378955


   We would like a couple meetings if possible - I would expect 5-10 min.

  1.  Heads up review of the spec and the diff  from Beijing - the MDC and 
Marker changes and proposed EPICs for Casablanca - would like to get this up 
for discussion earlier.
  2.  Demo: When we have some concrete running demo code finished and have 
prioritized/sized and agreed on the Casablanca epics - we could do another 
review the week after if possible. Discuss impact to teams, working with teams 
to implement, staged migration...


Team, Luke Parker, Shishir Thakore, Sanjay Agraharam, Neal Chatterley, Dave 
Williamson, Lee Bresleau, Xuan Liu, Horace Ip, Bob Ferro, David Bainbridge, 
Jimmy Forsyth.

   Thank you
/michael


This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

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

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

[onap-discuss] [ONAP Helpdesk #55152] [linuxfoundation.org #55152] Re: [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April

[dt5...@att.com via RT]

All,

You shouldn’t really be using snapshot versions of the CCSDK docker images.  
You should be using version 0.2-STAGING-latest for CCSDK (and 
1.3-STAGING-latest for SDN-C)

I noticed last week that the docker version manifest incorrectly specified 
snapshot versions for the CCSDK docker images, so I fixed that.   Sorry if that 
caused any confusion.

Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.

From:  on behalf of "OBRIEN, FRANK 
MICHAEL" 
Date: Monday, May 7, 2018 at 7:52 AM
To: "'onap-rele...@lists.onap.org'" , onap-discuss 

Cc: "'helpd...@onap.org'" 
Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT 
until 20 April

Team,
   The image was deleted again – looks like as James M. has mentioned – the 
rule for nexus3 deletion should be “delete 2 week old images – unless there has 
been no build in the past 2 weeks” – to keep at least 1 snapshot around

http://jenkins.onap.info/job/oom-cd-master/2880/console

10:54:55 onap  onap-appc-dgbuilder-6bbd4dbdcd-xwq7k 
 0/1   ImagePullBackOff   0  1h10.42.75.136
ip-10-0-0-136.us-east-2.compute.internal


10:54:55 onap  onap-sdnc-dgbuilder-76589b66b6-bwpk2 
 0/1   ImagePullBackOff   0  1h10.42.68.150
ip-10-0-0-136.us-east-2.compute.internal


Warning Failed 5m (x14 over 2h) kubelet, 
ip-10-0-0-136.us-east-2.compute.internal Failed to pull image 
"nexus3.onap.org:10001/onap/ccsdk-dgbuilder-image:0.2.1-SNAPSHOT": rpc error: 
code = Unknown desc = Tag 0.2.1-SNAPSHOT not found in repository 
nexus3.onap.org:10001/onap/ccsdk-dgbuilder-image

/michael

From: Michael O'Brien
Sent: Tuesday, April 24, 2018 5:19 PM
To: onap-rele...@lists.onap.org; onap-discuss@lists.onap.org
Cc: helpd...@onap.org
Subject: [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April

LF,
  Just would like to understand what happened to this image that broke SDNC and 
APPC for a couple days

https://jira.onap.org/browse/SDNC-285
https://jira.onap.org/browse/APPC-856

  From the logs it looks like the SNAPSHOT image was returned 4 days ago – 
before the 20th of April the dockers failed to pull.
https://nexus3.onap.org/#browse/browse:docker.snapshot:v2%2Fonap%2Fccsdk-dgbuilder-image%2Fmanifests%2F0.2.1-SNAPSHOT

Blob created

Fri Apr 20 2018 09:11:26 GMT-0400 (Eastern Daylight Time)

Blob updated

Tue Apr 24 2018 09:27:11 GMT-0400 (Eastern Daylight Time)


  When these images disappear for a while – the pods fail to come up.



  Thank you
  /michael
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer

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

Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April

[TIMONEY, DAN]

All,

You shouldn’t really be using snapshot versions of the CCSDK docker images.  
You should be using version 0.2-STAGING-latest for CCSDK (and 
1.3-STAGING-latest for SDN-C)

I noticed last week that the docker version manifest incorrectly specified 
snapshot versions for the CCSDK docker images, so I fixed that.   Sorry if that 
caused any confusion.

Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.

From:  on behalf of "OBRIEN, FRANK 
MICHAEL" 
Date: Monday, May 7, 2018 at 7:52 AM
To: "'onap-rele...@lists.onap.org'" , onap-discuss 

Cc: "'helpd...@onap.org'" 
Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT 
until 20 April

Team,
   The image was deleted again – looks like as James M. has mentioned – the 
rule for nexus3 deletion should be “delete 2 week old images – unless there has 
been no build in the past 2 weeks” – to keep at least 1 snapshot around

http://jenkins.onap.info/job/oom-cd-master/2880/console

10:54:55 onap  onap-appc-dgbuilder-6bbd4dbdcd-xwq7k 
 0/1   ImagePullBackOff   0  1h10.42.75.136
ip-10-0-0-136.us-east-2.compute.internal


10:54:55 onap  onap-sdnc-dgbuilder-76589b66b6-bwpk2 
 0/1   ImagePullBackOff   0  1h10.42.68.150
ip-10-0-0-136.us-east-2.compute.internal


Warning Failed 5m (x14 over 2h) kubelet, 
ip-10-0-0-136.us-east-2.compute.internal Failed to pull image 
"nexus3.onap.org:10001/onap/ccsdk-dgbuilder-image:0.2.1-SNAPSHOT": rpc error: 
code = Unknown desc = Tag 0.2.1-SNAPSHOT not found in repository 
nexus3.onap.org:10001/onap/ccsdk-dgbuilder-image

/michael

From: Michael O'Brien
Sent: Tuesday, April 24, 2018 5:19 PM
To: onap-rele...@lists.onap.org; onap-discuss@lists.onap.org
Cc: helpd...@onap.org
Subject: [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April

LF,
  Just would like to understand what happened to this image that broke SDNC and 
APPC for a couple days

https://jira.onap.org/browse/SDNC-285
https://jira.onap.org/browse/APPC-856

  From the logs it looks like the SNAPSHOT image was returned 4 days ago – 
before the 20th of April the dockers failed to pull.
https://nexus3.onap.org/#browse/browse:docker.snapshot:v2%2Fonap%2Fccsdk-dgbuilder-image%2Fmanifests%2F0.2.1-SNAPSHOT

Blob created

Fri Apr 20 2018 09:11:26 GMT-0400 (Eastern Daylight Time)

Blob updated

Tue Apr 24 2018 09:27:11 GMT-0400 (Eastern Daylight Time)


  When these images disappear for a while – the pods fail to come up.



  Thank you
  /michael
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [multicloud] cancel the meetings of 5:00 PST in May

[Xinhui Li]

Thanks for your attention and contribution to this project.  In this month, the 
team have been working integration, bug fix, and test framework improvement. So 
I canceled this meeting.  Please send me email any time if you have any special 
topics to discuss. I would like to maintain the queue and schedule group 
discussion like VNFC template sample, Azure template discussion when the focal 
persons feel ready.

I have been doing the bug triage and we have solved below problems in past 
weeks. Please send me email if you would like to help bug fix or test framework 
improvement or document enrichment. Thanks
(1) fixed health check
(2) fixed image version
(3) fixed openstack nova RabbitMQ message bump

(4) Support inject many files

(5) Fix inject file error

(6) Fix port creation for multiple IP address



At your service,

Xinhui Li

PTL of Multi VIM/Cloud

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

[onap-discuss] Canceled event: [multicloud] Weekly Meeting (Updated April 23, 2018) @ Mon May 28, 2018 5pm - 6pm (PDT) (onap-discuss@lists.onap.org)

[kpaul]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20180528T17
DTEND;TZID=America/Los_Angeles:20180528T18
DTSTAMP:20180507T125204Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:6ohoh3cu87m7q7dof9u9hlm...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=on
 ap-disc...@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@lists.onap.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=lx
 in...@vmware.com;X-NUM-GUESTS=0:mailto:lxin...@vmware.com
RECURRENCE-ID;TZID=America/Los_Angeles:20180528T17
CREATED:20180423T125457Z
DESCRIPTION:IFro
 m PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/
 9057041886" rel="nofollow" style="color: rgb(53\, 114\, 176)\; text-decorat
 ion: none\;">https://zoom.us/j/9057041886iPhone one-tap (US Toll): +16465588656\,\,9057041886
 # or +14086380968\,\,9057041886#Telephone:Dial: 
 +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)+1 855 880 1246 (US Toll Free)+1 877 369 0926 (US Toll Free)Meeting ID: 905 704 1886
LAST-MODIFIED:20180507T125204Z
LOCATION:https://zoom.us/j/9057041886
SEQUENCE:1
STATUS:CANCELLED
SUMMARY:[multicloud] Weekly Meeting (Updated April 23\, 2018)
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Canceled event: [multicloud] Weekly Meeting (Updated April 23, 2018) @ Mon May 21, 2018 5pm - 6pm (PDT) (onap-discuss@lists.onap.org)

[kpaul]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20180521T17
DTEND;TZID=America/Los_Angeles:20180521T18
DTSTAMP:20180507T125146Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:6ohoh3cu87m7q7dof9u9hlm...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=on
 ap-disc...@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@lists.onap.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=lx
 in...@vmware.com;X-NUM-GUESTS=0:mailto:lxin...@vmware.com
RECURRENCE-ID;TZID=America/Los_Angeles:20180521T17
CREATED:20180423T125457Z
DESCRIPTION:IFro
 m PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/
 9057041886" rel="nofollow" style="color: rgb(53\, 114\, 176)\; text-decorat
 ion: none\;">https://zoom.us/j/9057041886iPhone one-tap (US Toll): +16465588656\,\,9057041886
 # or +14086380968\,\,9057041886#Telephone:Dial: 
 +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)+1 855 880 1246 (US Toll Free)+1 877 369 0926 (US Toll Free)Meeting ID: 905 704 1886
LAST-MODIFIED:20180507T125146Z
LOCATION:https://zoom.us/j/9057041886
SEQUENCE:1
STATUS:CANCELLED
SUMMARY:[multicloud] Weekly Meeting (Updated April 23\, 2018)
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Canceled event: [multicloud] Weekly Meeting (Updated April 23, 2018) @ Mon May 14, 2018 5pm - 6pm (PDT) (onap-discuss@lists.onap.org)

[kpaul]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20180514T17
DTEND;TZID=America/Los_Angeles:20180514T18
DTSTAMP:20180507T125125Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:6ohoh3cu87m7q7dof9u9hlm...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=on
 ap-disc...@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@lists.onap.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=lx
 in...@vmware.com;X-NUM-GUESTS=0:mailto:lxin...@vmware.com
RECURRENCE-ID;TZID=America/Los_Angeles:20180514T17
CREATED:20180423T125457Z
DESCRIPTION:IFro
 m PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/
 9057041886" rel="nofollow" style="color: rgb(53\, 114\, 176)\; text-decorat
 ion: none\;">https://zoom.us/j/9057041886iPhone one-tap (US Toll): +16465588656\,\,9057041886
 # or +14086380968\,\,9057041886#Telephone:Dial: 
 +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)+1 855 880 1246 (US Toll Free)+1 877 369 0926 (US Toll Free)Meeting ID: 905 704 1886
LAST-MODIFIED:20180507T125125Z
LOCATION:https://zoom.us/j/9057041886
SEQUENCE:1
STATUS:CANCELLED
SUMMARY:[multicloud] Weekly Meeting (Updated April 23\, 2018)
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Canceled event: [multicloud] Weekly Meeting (Updated April 23, 2018) @ Mon May 7, 2018 5pm - 6pm (PDT) (onap-discuss@lists.onap.org)

[kpaul]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20180507T17
DTEND;TZID=America/Los_Angeles:20180507T18
DTSTAMP:20180507T125107Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:6ohoh3cu87m7q7dof9u9hlm...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=lx
 in...@vmware.com;X-NUM-GUESTS=0:mailto:lxin...@vmware.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=on
 ap-disc...@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@lists.onap.org
RECURRENCE-ID;TZID=America/Los_Angeles:20180507T17
CREATED:20180423T125457Z
DESCRIPTION:IFro
 m PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/
 9057041886" rel="nofollow" style="color: rgb(53\, 114\, 176)\; text-decorat
 ion: none\;">https://zoom.us/j/9057041886iPhone one-tap (US Toll): +16465588656\,\,9057041886
 # or +14086380968\,\,9057041886#Telephone:Dial: 
 +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)+1 855 880 1246 (US Toll Free)+1 877 369 0926 (US Toll Free)Meeting ID: 905 704 1886
LAST-MODIFIED:20180507T125107Z
LOCATION:https://zoom.us/j/9057041886
SEQUENCE:1
STATUS:CANCELLED
SUMMARY:[multicloud] Weekly Meeting (Updated April 23\, 2018)
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Canceled event: [sdc] Weekly #1 @ Mon May 7, 2018 7am - 8am (PDT) (onap-discuss@lists.onap.org)

[kpaul]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20180507T07
DTEND;TZID=America/Los_Angeles:20180507T08
DTSTAMP:20180507T124805Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:frslg51tcsf4fsr6c7c61lb...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ml
 6...@intl.att.com;X-NUM-GUESTS=0:mailto:ml6...@intl.att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=on
 ap-disc...@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@lists.onap.org
RECURRENCE-ID;TZID=America/Los_Angeles:20180507T07
CREATED:20170710T130629Z
DESCRIPTION:Hi there\, \n\nONAP Meeting 4 is inviting you to a scheduled Zo
 om meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.u
 s/j/489989304\n\nOr iPhone one-tap (US Toll):  +14086380968\,\,489989304# o
 r +16465588656\,\,489989304#\n\nOr Telephone:\nDial: +1 408 638 0968 (U
 S Toll) or +1 646 558 8656 (US Toll)\n+1 855 880 1246 (US Toll Free)\n 
+1 877 369 0926 (US Toll Free)\nMeeting ID: 489 989 304\nInterna
 tional numbers available: https://zoom.us/zoomconference?m=aBHgZkfSu_j-URGx
 XCTMLZ2_0FUeopNH\n\n
LAST-MODIFIED:20180507T124805Z
LOCATION:https://zoom.us/j/489989304
SEQUENCE:2
STATUS:CANCELLED
SUMMARY:[sdc] Weekly #1
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Updated Invitation: [sdc] Weekly #1 @ Weekly from 7am to 8am on Monday (PDT) (ml6...@intl.att.com)

[Lando,Michael]

Hi,

I apologize for the late update but todays SDC weekly is canceled.










BR,



AT Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
···
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: michael.la...@intl.att.com


-Original Appointment-
From: ONAP Meetings and Events 

Sent: Saturday, September 02, 2017 01:53
To: 'ONAP Meetings and Events'; Lando,Michael; onap-discuss@lists.onap.org
Subject: Updated Invitation: [sdc] Weekly #1 @ Weekly from 7am to 8am on Monday 
(PDT) (ml6...@intl.att.com)
When: Monday, May 07, 2018 7:00-8:00 America/Los_Angeles.
Where: https://zoom.us/j/489989304


This event has been changed.
more details 
»

[sdc] Weekly #1
When
Changed: Weekly from 7am to 8am on Monday Pacific Time

Where

https://zoom.us/j/489989304
 
(map)

Calendar
ml6...@intl.att.com

Who
•
kp...@linuxfoundation.org - creator

•
ml6...@intl.att.com

•
onap-discuss@lists.onap.org



Hi there,

ONAP Meeting 4 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/489989304
Or iPhone one-tap (US Toll): +14086380968,,489989304# or 
+16465588656,,489989304#
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: 489 989 304
International numbers available: 
https://zoom.us/zoomconference?m=aBHgZkfSu_j-URGxXCTMLZ2_0FUeopNH





Going?   All events in this series:   
Yes
 - 
Maybe
 - 

[onap-discuss] ONAP Wiki migration Issue

[GLOVER, GREG L]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Central Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="GLOVER, GREG L":MAILTO:gg2...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
DESCRIPTION;LANGUAGE=en-US:Discuss interim proposal for https://jira.onap.o
 rg/browse/DOC-264\n...
 ..
 \n--> Join Skype Meeting\nTrouble Joining? Try Skype Web App\nJoin by phone\n\n8443439499\, access code: 24468606 (USA\, Gl
 obal)   English (United States)\n8443439505\, access code:
  24468606 (USA\, Global)   English (United States)\n844433
 1206\, access code: 24468606 (USA\, Global)   English (Uni
 ted States)\n8447870853\, access code: 24468606 (USA\, Global)
English (United States)\n+1 (205) 517-4000\, access code: 24468606 
 (USA\, Global)English (United States)\n\nFind a lo
 cal number\n\nConference ID: 2446
 8606 (same as access code above)\nForgot your dial-in PIN? |Help\n\n[!OC([1033])!]\n..
 ..
 .\n\n
SUMMARY;LANGUAGE=en-US:ONAP Wiki migration Issue
DTSTART;TZID=Central Standard Time:20180507T14
DTEND;TZID=Central Standard Time:20180507T143000
UID:04008200E00074C5B7101A82E0082026540BF7E2D301000
 01000ADD503EA0C64BE428E7161CDCB6396CA
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180507T120416Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:2
LOCATION;LANGUAGE=en-US:Skype Meeting
X-MICROSOFT-CDO-APPT-SEQUENCE:2
X-MICROSOFT-CDO-OWNERAPPTID:1732466658
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [ONAP Helpdesk #55152] [linuxfoundation.org #55152] RE: [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April

[Michael O'Brien via RT]

Team,
   The image was deleted again - looks like as James M. has mentioned - the 
rule for nexus3 deletion should be "delete 2 week old images - unless there has 
been no build in the past 2 weeks" - to keep at least 1 snapshot around

http://jenkins.onap.info/job/oom-cd-master/2880/console

10:54:55 onap  onap-appc-dgbuilder-6bbd4dbdcd-xwq7k 
 0/1   ImagePullBackOff   0  1h10.42.75.136
ip-10-0-0-136.us-east-2.compute.internal


10:54:55 onap  onap-sdnc-dgbuilder-76589b66b6-bwpk2 
 0/1   ImagePullBackOff   0  1h10.42.68.150
ip-10-0-0-136.us-east-2.compute.internal


Warning Failed 5m (x14 over 2h) kubelet, 
ip-10-0-0-136.us-east-2.compute.internal Failed to pull image 
"nexus3.onap.org:10001/onap/ccsdk-dgbuilder-image:0.2.1-SNAPSHOT": rpc error: 
code = Unknown desc = Tag 0.2.1-SNAPSHOT not found in repository 
nexus3.onap.org:10001/onap/ccsdk-dgbuilder-image

/michael

From: Michael O'Brien
Sent: Tuesday, April 24, 2018 5:19 PM
To: onap-rele...@lists.onap.org; onap-discuss@lists.onap.org
Cc: helpd...@onap.org
Subject: [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April

LF,
  Just would like to understand what happened to this image that broke SDNC and 
APPC for a couple days

https://jira.onap.org/browse/SDNC-285
https://jira.onap.org/browse/APPC-856

  From the logs it looks like the SNAPSHOT image was returned 4 days ago - 
before the 20th of April the dockers failed to pull.
https://nexus3.onap.org/#browse/browse:docker.snapshot:v2%2Fonap%2Fccsdk-dgbuilder-image%2Fmanifests%2F0.2.1-SNAPSHOT

Blob created

Fri Apr 20 2018 09:11:26 GMT-0400 (Eastern Daylight Time)

Blob updated

Tue Apr 24 2018 09:27:11 GMT-0400 (Eastern Daylight Time)


  When these images disappear for a while - the pods fail to come up.



  Thank you
  /michael
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

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


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

Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April

[Michael O'Brien]

Team,
   The image was deleted again - looks like as James M. has mentioned - the 
rule for nexus3 deletion should be "delete 2 week old images - unless there has 
been no build in the past 2 weeks" - to keep at least 1 snapshot around

http://jenkins.onap.info/job/oom-cd-master/2880/console

10:54:55 onap  onap-appc-dgbuilder-6bbd4dbdcd-xwq7k 
 0/1   ImagePullBackOff   0  1h10.42.75.136
ip-10-0-0-136.us-east-2.compute.internal


10:54:55 onap  onap-sdnc-dgbuilder-76589b66b6-bwpk2 
 0/1   ImagePullBackOff   0  1h10.42.68.150
ip-10-0-0-136.us-east-2.compute.internal


Warning Failed 5m (x14 over 2h) kubelet, 
ip-10-0-0-136.us-east-2.compute.internal Failed to pull image 
"nexus3.onap.org:10001/onap/ccsdk-dgbuilder-image:0.2.1-SNAPSHOT": rpc error: 
code = Unknown desc = Tag 0.2.1-SNAPSHOT not found in repository 
nexus3.onap.org:10001/onap/ccsdk-dgbuilder-image

/michael

From: Michael O'Brien
Sent: Tuesday, April 24, 2018 5:19 PM
To: onap-rele...@lists.onap.org; onap-discuss@lists.onap.org
Cc: helpd...@onap.org
Subject: [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April

LF,
  Just would like to understand what happened to this image that broke SDNC and 
APPC for a couple days

https://jira.onap.org/browse/SDNC-285
https://jira.onap.org/browse/APPC-856

  From the logs it looks like the SNAPSHOT image was returned 4 days ago - 
before the 20th of April the dockers failed to pull.
https://nexus3.onap.org/#browse/browse:docker.snapshot:v2%2Fonap%2Fccsdk-dgbuilder-image%2Fmanifests%2F0.2.1-SNAPSHOT

Blob created

Fri Apr 20 2018 09:11:26 GMT-0400 (Eastern Daylight Time)

Blob updated

Tue Apr 24 2018 09:27:11 GMT-0400 (Eastern Daylight Time)


  When these images disappear for a while - the pods fail to come up.



  Thank you
  /michael
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

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

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

Re: [onap-discuss] OOM deployment error

[Mohan Kumar]

Vijay ,

Try to upgrade your helm version to 2.8.2. This solved above issue in my
environment

wget
http://storage.googleapis.com/kubernetes-helm/helm-v2.8.2-linux-amd64.tar.gz
tar -xvf helm-v2.8.2-linux-amd64.tar.gz
sudo mv linux-amd64/helm /usr/local/bin
rm -f helm-v2.8.2-linux-amd64.tar.gz
rm -rf linux-amd64

Thanks.,
Mohankumar.N

On Thu, May 3, 2018 at 6:35 PM, VENKATESH KUMAR, VIJAY 
wrote:

> OOM Team,
>
> While deploying the latest (master) OOM charts, running into below error.
>
>
>
> ubuntu@vv-k8-2:~/oom/kubernetes$  helm install local/onap -n dev
> --namespace onap
>
> 2018/05/03 02:36:05 warning: skipped value for image: Not a table.
>
> Error: error validating "": error validating data: found invalid field
> annotations for v1.PersistentVolumeClaim
>
>
>
>
>
> Any suggestions please?
>
>
>
> Regards,
>
> Vijay
>
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-discuss
>
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] ONAP platform deployment no successful

[Santi Rodríguez]

Hi Hector A,

thank you for your response.



*Santiago Rodríguez García* | Senior Analyst
T/ + 34 986 410 091 (ext) 227
www.optaresolutions.com
[image: Optare Solutions] 

2018-04-25 1:13 GMT+02:00 ANAPAN-LAVALLE, HECTOR A :

> Hi Santi,
>
>
>
> For the Amsterdam release:
>
>
>
> -I have come across that same error when I deployed ONAP in a 
> multi-node/vm HA Kubernetes version of Rancher 
> (https://rancher.com/docs/rancher/v1.6/en/kubernetes/resiliency-planes/) but 
> not when the K8S cluster is hosted on a single VM only, so wondering if you 
> tried doing this. One thing to make sure is to try using the latest supported 
> version of docker for rancher which is 17.03.x I believe 
> (https://rancher.com/docs/rancher/v1.6/en/hosts/#supported-docker-versions).
>
> -Also, I used the README.md when installing ONAP using the OOM Amsterdam 
> release (running createConfig.sh -n onap to create the namespace first, then 
> running createAll.sh -n onap to create the ONAP instance)
>
>
>
>
>
> For the Beijing release:
>
>
>
> -While the code is not stable enough yet, there was an issue with the 
> docker image registry (nexus3.onap.org) for the past few weeks but my 
> understanding is that it has been solved.
>
> -Also, you may want to look into having a local docker proxy that pulls 
> the images from the LF docker registry to pull the images faster and more 
> consistently (https://docs.docker.com/registry/recipes/mirror/). Another 
> option is to download your own local nexus3 OSS repo in its own instance, and 
> use it as a docker registry to proxy the images from nexus3.onap.org.
>
>
>
> =
>
> =
>
> =
>
>
>
>
>
>
>
> Hi all,
>
>
>
> I've been trying to deploy the ONAP entire platform in my local environment
>
> following the official documentation without the desired results:
>
>
>
>- First, I tried the amsterdam release installation:
>
>   - kubectl 1.7.7
>
>   - rancher 1.6.10
>
>   - helm 2.3.0
>
>   - docker 1.12
>
>   - onap deployment using oom:
>
>  - install/deployment/cd.sh
>
>  - oom/kubernetes/oneclick/createAll.sh
>
>
>
> Some of the pods are returning errors like:
>
>
>
> Error syncing pod
>
> Back-off restarting failed container
>
> (combined from similar events): Error: failed to start container
>
> "filebeat-onap-aai-model-loader": Error response from daemon:
>
> {"*message":"invalid
>
> header field value* \"oci runtime error: container_linux.go:247: starting
>
> container process caused \\\"process_linux.go:359: container init caused
>
> \\\"rootfs_linux.go:53: mounting
>
> \\\"/dockerdata-nfs/onap/log/filebeat/logback/filebeat.yml\\\"
>
> to rootfs
>
> \\\"/var/lib/docker/aufs/mnt/5c0516a9e0641c993fda14a5818d53b59ff4342da146d52a3b58aaf045ce6295\\\"
>
> at
>
> \\\"/var/lib/docker/aufs/mnt/5c0516a9e0641c993fda14a5818d53b59ff4342da146d52a3b58aaf045ce6295/usr/share/filebeat/filebeat.yml\\\"
>
> caused \\\"not a directory\\\"\\\"\\\"\\n\""}
>
>
>
>
>
>- Then, I tried with beijing/master:
>
>   - kubectl 1.8.6
>
>   - rancher 1.6.14
>
>   - helm 2.6.1
>
>   - docker 17.03
>
>   - onap deployment using helm install local/onap
>
>
>
> Some of the pods are not starting because they cannot pull the image. It
>
> seems that large images produces a timeout. I found something related with
>
> increasing a kubelet config parameter, but the followed k8s installation
>
> guide does not produce any kubelet installation.
>
>
>
> It seems that the code is not stable enough, but i saw that many people are
>
> working with the platform so is possible to deploy it.
>
>
>
> How did you deploy the platform? Is there any hidden step that I'm missing?
>
>
>
> Thanks,
>
>
>
> BR, Santi
>
> *Santiago Rodríguez García* | Senior Analyst
>
> T/ + 34 986 410 091 (ext) 227
>
> www.optaresolutions.com
>
> [image: Optare Solutions] 
>
> -- next part --
>
> An HTML attachment was scrubbed...
>
> URL: 
> 
>
>
>
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-discuss
>
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Kibana administrator contact

[Migdal, Marcin (Nokia - PL/Wroclaw)]

Hello,


Could anyone please point me to Kibana administartor?

https://onap.biterg.io/app/kibana


I cannot see myself attached to my company in commits' statistics.

Also new projects are not attached to Kibana automatically.

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