Re: [onap-discuss] Issues with Kubectl setup and newly pulleddockers not showing in kubectl list ---namespace

[li.zi30]

Thank you gaurav to raise the ticket about ESR.




Hi Michael,




I've commit the script about deploy ESR dockers with OOM. Could you please 
review it? See https://gerrit.onap.org/r/#/c/25771/ 




Thank you,

LiZi







原始邮件



发件人： ;
收件人： ; ;
日 期 ：2017年12月08日 01:31
主 题 ：Re: [onap-discuss] Issues with Kubectl setup and newly pulleddockers not 
showing in kubectl list ---namespace


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

  



Thanks Michael . 



 


a. For Kubectl - we ensured that version 1.7.0 is installed because this is the 
version that we have in our kubernetes cluster . 


   but we are still struggling a little bit with Kubectl 
configuration . In terms of what should work where . 



 





root@localhost:~# kubectl cluster-info
Kubernetes master is running at https://10.110.208.207:443/
dnsmasq is running at 
https://10.110.208.207:443//api/v1/namespaces/kube-system/services/dnsmasq/proxy
kubedns is running at 
https://10.110.208.207:443//api/v1/namespaces/kube-system/services/kubedns/proxy

 b For mixup of dockers for esr - We raised JIRA Ticket  
https://jira.onap.org/browse/OOM-493 .
 





 


this is the  understanding that we have  -- 

1  kubernetes cluster , 

2  install Kubectl , 

3.  install  Helm 

prior to doing GIT Clone for OOM  .
 
 is there any thing else that we should be doing prior GIT Clone . thanks to 
confirm .
 
 with best regards

gaurav 


From: onap-discuss-boun...@lists.onap.org  
on behalf of Michael O'Brien 
 Sent: 07 December 2017 06:28:43
 To: onap-discuss@lists.onap.org
 Subject: Re: [onap-discuss] Issues with Kubectl setup and newly pulled dockers 
not showing in kubectl list ---namespace  



Guarav,


   Hi, some more points – and I hope your demo went well and thanks again for 
raising all the issues that helped us fix up the Amsterdam branh.


 


1)  Kubectl 1.7.0 vs supported 1.8.4 – I suspect this is your issue.


  I last ran the following bootstrap script at noon on a lean machine and after 
running cd.sh had a system up after the prepull in 23 min with no issues except 
 for the known aaf container.


https://github.com/obrienlabs/onap-root/blob/master/oom_rancher_setup_1.sh


   Your issue may be the version of kubectl – our currently stable release 
config is as follows on the page 
https://wiki.onap.org/display/DW/ONAP+on+Kubernetes#ONAPonKubernetes-QuickstartInstallation
 


 


Rancher v1.6.10 (not the stable or latest tag)


Helm 2.3.0 on the server and client


Kubectl 1.8.4 (current stable version) – yours is 1.7.0  (I have seen 1.8.8 
running)


 


You should be running



curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl  -s 
https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl



 


2)  Mixing raw dockers with Kubernetes managed containers


You will need a JIRA to add the Kubernetes infrastructure for AAI ESR – I don’t 
see the containers in HEAT either (aai1/aai2)


 As Alexis stated: If you need a new component – it must have a yaml set and 
deleted/created via the scripts or directly with helm – in HELM_APPS –  esr is 
not there.


  Mixing raw docker run commands or docker-compose up – will be outside the 
“onap” namespace setup by kubernetes – they can run independently and be 
accessed  - but they will be out of the 30xxx namespace – as in not managed by 
Kubernetes.   ESR would need a config set, a set of template yamls, an 
all-services.yaml to set the external port mappings, a Chart.yaml for helm and 
a values.yaml to list the docker images and their version tags. 


   As I remember ESR (External System Registrar) is part of AAI  portal 
onboarding – I did see these two images in the older manifest but currently the 
 9 container AAI pod does not have a definition for ESR.


https://gerrit.onap.org/r/gitweb?p=integration.git;a=blob;f=version-manifest/src/main/resources/docker-manifest.csv;h=35e992adc0678ccd98328d33c9a5ffc88dbb4dfa;hb=refs/heads/master


 


 


For a reference Amsterdam install to check on – see the live CD server


And the healthcheck references  (Thanks to Shane Daniel in adding this 
dashboard to the elk stack)


 


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


 


 

Re: [onap-discuss] About Image Manager Project Proposal

[Gildas Lanilis]

Hi Huabing,

Thanks for the notice.
Could you ensure the project proposal is visible into the “Proposed Project” at 
https://wiki.onap.org/display/DW/Proposed+Projects (most probably you will just 
need to use the move capability of Confluence)?

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn]
Sent: Thursday, December 07, 2017 9:03 PM
To: Gildas Lanilis 
Cc: onap-...@lists.onap.org; onap-discuss@lists.onap.org
Subject: About Image Manager Project Proposal


Hi Gildas and all,



I have requested to defer the Image Manager Project proposal at this week's TSC 
meeting. But after that, we receive some feedback from the community that the 
requirements of Image Manager is important for operators.

So we'd like to add this project back to the F2F project proposal agenda to 
discuss with the TSC and figure out the way going forward.



Thanks,

Huabing








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

Re: [onap-discuss] [onap-tsc] Bridges for next week.

[Sabater, Susana, Vodafone Spain]

Hi Kenny,
Do we have the bridges set up? For Monday morning we expect to have some remote 
participants. Could you please confirm this will be possible?

Cheers
/Susana

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Kenny Paul
Sent: Thursday, December 7, 2017 7:26 PM
To: onap-discuss@lists.onap.org; onap-...@lists.onap.org
Subject: [onap-tsc] Bridges for next week.

Yes there will be dial-ins.
No, I have not set them up yet.
Yes, I will send mail when I’ve done so.

Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

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

[onap-discuss] huddle room updates

[Kenny Paul]

I know that there are a few huddle room updates pending updates in Sched.  I 
have a hard deliverable for the ONAP board today. I will be making Sched 
updates after I’ve completed the work for the Board which will take me most of 
the day.


Best Regards, 
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

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

Re: [onap-discuss] [OpenLab]Add dns designate for OOM tenant

[Alexis de Talhouët]

Hi Bin,
Thanks for the answer. I think I was able to successfully deploy the onap HEAT 
stack in the OOM tenant, with DCAE.
Alexis

> On Dec 7, 2017, at 7:59 PM, Yang, Bin  wrote:
> 
> Hi Alexis,
> 
>   DNS designate has been deployed on another small stack (10.12.25.5) and 
> proxied by multicloud service (the micro service named multicloud-windriver) 
> .  The cloud-regions (pod25 and pod25dns) should be registered by DCAE 
> bootstrap. If you have the multicloud-windriver service DCAE bootstrap 
> running then you should be good to go. (I made sure that the surrogate tenant 
> OOM and demo user as its user be ready)
> 
> Best Regards,
> Bin Yang,Solution Readiness Team,Wind River
> Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
> Skype: yangbincs993
> 
> -Original Message-
> From: onap-discuss-boun...@lists.onap.org 
> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alexis de Talhouët
> Sent: Friday, December 08, 2017 6:29 AM
> To: onap-discuss@lists.onap.org; Gooch, Stephen
> Subject: [onap-discuss] [OpenLab]Add dns designate for OOM tenant
> 
> Hi Stephen, team,
> 
> I’m under the impression DNS  designate is not enable for OOM tenant. Could 
> you verify it is, else enable it for OOM tenant?
> I got an error saying the plugin isn’t enabled.
> 
> Thanks,
> Alexis
> 
> Sent from my iPhone
> ___
> 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] [integration][dcae] ONAP instance in DCAE tenant

[Yunxia Chen]

Hi, Lusheng,
Are you testing anything in DCAE tenant? I saw a full stack of ONAP, but it was 
from 1+ month or two weeks ago. If not, could you please delete or stop them, 
we are running out of resource in Integration lab.

Regards,
Helen Chen

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

Re: [onap-discuss] successful vFW instantiation with k8s ONAP

[Alexis de Talhouët]

Hi Marco, 

All the fixes has been pushed. If you’d like to help validate them, that’d be 
great. I’m trying to get DCAE up with OOM now.

- demo.sh and ete.sh not up to date —> https://gerrit.onap.org/r/#/c/25819/1 

- I can see the mount point in APPC GUI. Note, this might be an ODL bug, see 
https://git.opendaylight.org/gerrit/#/c/64610/ 
 that was just fixed. Sometimes 
you have to reload, or try many times.
- the update op policy script for OOM —> https://gerrit.onap.org/r/#/c/25817/ 


And in addition to that, many fixes in the policy module of OOM: 
https://gerrit.onap.org/r/#/c/25547/ 

Thanks,
Alexis

> On Dec 5, 2017, at 11:14 AM, PLATANIA, MARCO (MARCO) 
> > wrote:
> 
> OOM Team, All,
>  
> I was able to successfully instantiate the vFW VNF using an ONAP instance 
> installed via OOM K8s in my private lab. Please see the attached screenshot.
>  
> Thanks to OOM Team for making such a great progress so fast!
>  
> There are still a few issues that I want to highlight, so once they will get 
> fixed we can test the entire closed loop:
> · The demo.sh and ete.sh scripts in $OOM_HOME/kubernetes/robot aren’t 
> the latest. In particular, demo.sh doesn’t have instructions to run 
> heatbridge, which is necessary to complete closed loop.
> · Although I mounted the vPacketGen interface in APPC, I can’t see 
> the mount point in the APPC GUI. Not sure why this happens. Can it be a 
> miscommunication between APPC containers? I’m using a 2-VM cluster, with APPC 
> containers spread across the two VMs.
> · We built a script that updates the operational policy for the vFW 
> closed look. It’s in the demo repository: 
> $DEMO_HOME/vnfs/vfw/scripts/update-vfw-op-policy.sh. We should find a way to 
> onboard it into some OOM directory, pretty much as with robot scripts 
> (although other components like CLAMP could be used for updating policies).
>  
> Thanks,
> Marco
>  
>  
>  
> ___
> 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] [Integration] Important reminder on Open Lab usage

[Alexis de Talhouët]

Hi Helen,

Ok cool, let me know in case you need resources for the demo.
No, the only instances I created are in the OOM tenant. I only use this tenant. 
So instances in the “Integration” tenant are not mine.

Thanks,
Alexis

> On Dec 8, 2017, at 10:54 AM, Yunxia Chen  wrote:
> 
> Hi, Alexis,
> Thanks for letting us know that. We are working on getting more resource. One 
> ONAP HEAT stack in OOM tenant should be fine at this moment unless we run 
> into issues again: we hope to have a smooth demo for next week.
>  
> Do you also use those instances in “Integration” tenant? I asked a few times, 
> no one response, if I still don’t hear anything by the end of today, I will 
> clean Integration space.
>  
> Regards,
>  
> Helen Chen
>  
> From:  on behalf of Alexis de Talhouët 
> 
> Date: Friday, December 8, 2017 at 7:46 AM
> To: Kang Xi 
> Cc: onap-discuss , "SHI, LEIMENG" 
> 
> Subject: Re: [onap-discuss] [Integration] Important reminder on Open Lab usage
>  
> Hi, 
>  
> I’ve just spawn a full ONAP HEAT stack within the OOM tenant so I can 
> properly make OOM works.
> If resources are missing, I could delete my stack and re-create it later.
> But keep in mind it is very important for OOM to have feature parity with the 
> HEAT setup ASAP so (non)official OOM Amsterdam branch can be created and 
> documented for external consumer.
>  
> Thanks,
> Alexis
> 
> 
> On Dec 8, 2017, at 10:40 AM, Kang Xi  > wrote:
>  
> Hi All,
>  
> The community open lab will be used to support multiple demos during next 
> week’s ONAP event. If you need to access any of the workspaces in the open 
> lab, please first double check with the corresponding workspace owner so as 
> to avoid accidents. If you don’t know the workspace owner please see details 
> here:https://wiki.onap.org/display/DW/Integration+Test+Labs 
> 
> If you still have questions please feel free to contact Helen Chen 
> helen.c...@huawei.com  or Kang Xi 
> kang...@huawei.com 
>  
> Many thanks for your support.
>  
> Regards,
> Kang
>  
> ___
> 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] [Integration] Important reminder on Open Lab usage

[Yunxia Chen]

Hi, Alexis,
Thanks for letting us know that. We are working on getting more resource. One 
ONAP HEAT stack in OOM tenant should be fine at this moment unless we run into 
issues again: we hope to have a smooth demo for next week.

Do you also use those instances in “Integration” tenant? I asked a few times, 
no one response, if I still don’t hear anything by the end of today, I will 
clean Integration space.

Regards,

Helen Chen

From:  on behalf of Alexis de Talhouët 

Date: Friday, December 8, 2017 at 7:46 AM
To: Kang Xi 
Cc: onap-discuss , "SHI, LEIMENG" 
Subject: Re: [onap-discuss] [Integration] Important reminder on Open Lab usage

Hi,

I’ve just spawn a full ONAP HEAT stack within the OOM tenant so I can properly 
make OOM works.
If resources are missing, I could delete my stack and re-create it later.
But keep in mind it is very important for OOM to have feature parity with the 
HEAT setup ASAP so (non)official OOM Amsterdam branch can be created and 
documented for external consumer.

Thanks,
Alexis


On Dec 8, 2017, at 10:40 AM, Kang Xi 
> wrote:

Hi All,

The community open lab will be used to support multiple demos during next 
week’s ONAP event. If you need to access any of the workspaces in the open lab, 
please first double check with the corresponding workspace owner so as to avoid 
accidents. If you don’t know the workspace owner please see details 
here:https://wiki.onap.org/display/DW/Integration+Test+Labs
If you still have questions please feel free to contact Helen Chen 
helen.c...@huawei.com or Kang Xi 
kang...@huawei.com

Many thanks for your support.

Regards,
Kang

___
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] [Integration] Important reminder on Open Lab usage

[Alexis de Talhouët]

Hi,

I’ve just spawn a full ONAP HEAT stack within the OOM tenant so I can properly 
make OOM works.
If resources are missing, I could delete my stack and re-create it later.
But keep in mind it is very important for OOM to have feature parity with the 
HEAT setup ASAP so (non)official OOM Amsterdam branch can be created and 
documented for external consumer.

Thanks,
Alexis

> On Dec 8, 2017, at 10:40 AM, Kang Xi  wrote:
> 
> Hi All,
>  
> The community open lab will be used to support multiple demos during next 
> week’s ONAP event. If you need to access any of the workspaces in the open 
> lab, please first double check with the corresponding workspace owner so as 
> to avoid accidents. If you don’t know the workspace owner please see details 
> here:https://wiki.onap.org/display/DW/Integration+Test+Labs 
> 
> If you still have questions please feel free to contact Helen Chen 
> helen.c...@huawei.com  or Kang Xi 
> kang...@huawei.com 
>  
> Many thanks for your support.
>  
> Regards,
> Kang
>  
> ___
> 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] [Integration] Important reminder on Open Lab usage

[Kang Xi]

Hi All,

The community open lab will be used to support multiple demos during next 
week's ONAP event. If you need to access any of the workspaces in the open lab, 
please first double check with the corresponding workspace owner so as to avoid 
accidents. If you don't know the workspace owner please see details here: 
https://wiki.onap.org/display/DW/Integration+Test+Labs
If you still have questions please feel free to contact Helen Chen 
helen.c...@huawei.com or Kang Xi 
kang...@huawei.com

Many thanks for your support.

Regards,
Kang

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

Re: [onap-discuss] [clamp] What is the difference between 'model' and 'template' in the Control Loop Design System?

[Ngueko, Gervais-Martial]

Hi,

A template is the generic description of a control loop flow (list the sequence 
of micro-services connection that compose that generic flow).

A model is an instance of a Control loop flow with the association of that flow 
(the template) with a Service. So ‘model’ = ‘template’ + ‘link to a specific 
service’ +configuration values (for a specific instance of a Control Loop) + 
’Operational policy’ (action to be executed by the Control Loop).
Note that the configuration value are actually materialized by special policies 
called ‘configuration policies’. Both Configuration and Operational policies 
resides inside the POLICY component of ONAP (CLAMP uses POLICY exposed API to 
create those policies).

Br,
Martial

From: yuan@zte.com.cn [mailto:yuan@zte.com.cn]
Sent: mardi 5 décembre 2017 10:32
To: Ngueko, Gervais-Martial ; SHACHAM, RON 

Cc: onap-discuss@lists.onap.org
Subject: [clamp] What is the difference between 'model' and 'template' in the 
Control Loop Design System?


Hi CLAMP team,



I found there are two terms 'model' and 'template' in the Control Loop Design 
System.

What is the difference. Can you give an example?



Thanks,

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

[onap-discuss] [multicloud] Multi Cloud Project Weekly Promotions

[Xinhui Li]

Hi,

A reminder here, our Multi Cloud weekly meeting has been moved to 5:00 AM 
pacific time. I would like to remind you to finish the doodle poll 
https://doodle.com/poll/4s5snzshutawrf3i if you are interested at Multi Cloud 
project and do not poll yet. Moreover, I encourage you to leave comments on 
your poll about if you want keep the current time as option or you want some 
time fit for your specific time zone.

The coming week is our ONAP Beijing Release Developer Forum. I would like to 
promote several topics/panels about Multi VIM/Cloud Project:

(1) Multi Cloud Evolvement in R2 for Carrier Grade Support
Tuesday, December 12 • 11:45am - 12:30pm, SC12-167-11

Multi VIM/Cloud team has successfully delivered R1. What is the right path and 
practical way to evolve forward and achieve the goal of carrier-grade in 
Beijing release? In this session, we will use a retrospective of R1 delivery 
cycle to elaborate an architectural design evolvement with consideration to 
both functional and non-functional perspectives for suggestions/comments.

(2) Achieving ONAP S3P with Standardized Object Model of Multi-Clouds
Tuesday, December 12 • 1:45pm - 2:30pm, Auditorium

Today multi cloud objects and their hierarchical relationships are modeled in a 
cloud-specific way creating inconsistent modeling of similar features across 
multi clouds. The challenge is in both data management and interoperability 
among ONAP components such as onboarding, policy management, orchestration, 
optimization etc. This presentation discusses standardized Information Models 
for multi cloud objects (Physical/Logical DC, Tenant, Cluster, Host, VM, 
Container etc.) in terms of capabilities (platform awareness etc.), resource 
reservation/utilization and other parameters for current and future cloud 
implementations. It also discusses the hierarchical relationships between those 
multi cloud objects. It illustrates how policy, data management and 
optimization frameworks can benefit from this standardization through concrete 
examples thus addressing the challenges of ONAP R2 & beyond.

(3) Enabling Workloads Orchestration in Containers via Multi Cloud
Wednesday, December 13 • 4:15pm - 4:50pm, Auditorium

Today ONAP OOM enables deployment of ONAP components as containerized micro 
services in a k8s cluster. On the other hand, workload deployment and 
orchestration in k8s clusters is expected to play an essential role in ONAP 
operational success. This presentation discusses an architectural vision of 
orchestrating workloads in container clusters via Multi Cloud. The key aspects 
for a comprehensive ONAP workloads orchestration are discussed, including 
deploying containerized workloads, e.g. VNFs [IETF NFVRG Talk], into k8s 
clusters on bare metal in edge cloud. ONAP Multi Cloud component serves as a 
single platform for deployment and orchestration of containerized workloads as 
well as classical VM-based workloads in true multiple infrastructures, 
including clouds, k8s on CaaS/cloud, k8s on bare metal, etc. It simplifies 
workload management and improves ONAP’s user experience.


(4) Towards a Comprehensive ONAP Operations Management Solution
December 11 • 5:00pm - 5:30pm SC12-175-38

Moreover, we will share one demo where VMware VIO 4.0 Cloud instance runs in 
the core data center hosting the ONAP components and vDNS VNF and a Wind River 
Titanium Cloud instance runs in the edge data center and hosts the vFW VNF.

Xinhui Li
PTL Multi Cloud





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