Mazin, Ref: https://lists.onap.org/pipermail/onap-discuss/2018-January/007085.html
HI, just a couple groups off the top of my head (also went quickly through a couple wikis, mails and jiras) that have been deploying ONAP via Kubernetes recently and also have been contributing to JIRAs and the WIKI – One focus could be will send a full list out later The short list of users/contributors to OOM bringing up ONAP on Kubernetes is Projects in bold - CLI, Integration, Logging-analytics, MSB, Multicloud, Optimization-Framework, SDNC, VFC In queue – AAI, APPC, SDC, VID, DCAEGEN2 Companies – Vmware, ARM, Amazon, Cloudify Orgs – OPNFV, CENGN SDNC (see K8S clustering work – as a scalability/resiliency RI) https://wiki.onap.org/display/DW/SDN-C+Clustering+on+Kubernetes https://wiki.onap.org/display/~jsulliva https://wiki.onap.org/display/~rahuliitr https://wiki.onap.org/display/~beiliz https://wiki.onap.org/display/~yavsare AAI The AAI team has contributed fixes for us directly into OOM – much appreciated Integration – https://wiki.onap.org/display/~bdfreeman1421 – as we know Brian has helped us immensely setup, runtime configuration and validates our config/runtime wiki https://wiki.onap.org/display/~gwu https://wiki.onap.org/display/~bdfreeman1421 https://wiki.onap.org/display/~djhunt https://wiki.onap.org/display/~platania https://wiki.onap.org/display/~GordonOlson https://wiki.onap.org/display/~Ranpollak MSB https://wiki.onap.org/display/~HuabingZhao – devops work CLI https://wiki.onap.org/display/~subhash_singh – devops work Multicloud https://wiki.onap.org/display/~liangke – devops work VFC https://wiki.onap.org/display/~maopengzhang – devops work DCAE https://wiki.onap.org/display/~vv770d - pending Logging-analytics – implemented in OOM https://wiki.onap.org/display/~shanedaniel https://wiki.onap.org/display/~jmac https://wiki.onap.org/display/~akhosla https://wiki.onap.org/display/~jbalasub VMware/OPNFV https://wiki.onap.org/display/~arun_arora https://wiki.onap.org/display/~guptagaurav https://wiki.onap.org/display/~ramkri123 Optimization Framework https://wiki.onap.org/display/~sisukapalli ARM/OPNFV/VNF-SDK https://wiki.opnfv.org/display/AUTO/Auto+Lab+Deployment Harry and Tina CENGN<https://www.cengn.ca/> https://wiki.onap.org/display/~srobillard – excellent container diagram Amazon https://wiki.onap.org/display/~ccionapdev Cloudify https://wiki.onap.org/display/~shayn https://wiki.onap.org/display/~ArthurBerezin OOM: Bell, Amdocs, AT&T Teams – part of OOM team – you already know – did not break out here ONAP members involved in bringing up/debugging the system – TEAM unknown https://wiki.onap.org/display/~mikden https://wiki.onap.org/display/~syedatifhusain https://wiki.onap.org/display/~namssob https://wiki.onap.org/display/~Vidhu https://wiki.onap.org/display/~Senshu555 https://wiki.onap.org/display/~atulan https://wiki.onap.org/display/~vaibhav_16dec https://wiki.onap.org/display/~peerless1230 https://wiki.onap.org/display/~tuanloc2503 https://wiki.onap.org/display/~Radhika_Kaslikar https://wiki.onap.org/display/~ehaselwanter https://wiki.onap.org/display/~virajput https://wiki.onap.org/display/~kowsalyagv https://wiki.onap.org/display/~rajeshm https://wiki.onap.org/display/~Premthinks https://wiki.onap.org/display/~gopinatht https://wiki.onap.org/display/~mohamedaly https://wiki.onap.org/display/~kirankamineni https://wiki.onap.org/display/~cnleng https://wiki.onap.org/display/~ForMartha https://wiki.onap.org/display/~SathvikManoj https://wiki.onap.org/display/~liangke https://wiki.onap.org/display/~nagaraja_sr https://wiki.onap.org/display/~zengjianguo https://wiki.onap.org/display/~tsadok https://wiki.onap.org/display/~beejals https://wiki.onap.org/display/~Pavithra_Radhakrishnan [email protected]<mailto:[email protected]> SDC/VID In queue under https://jira.onap.org/browse/SDC-828 and https://jira.onap.org/browse/VID-162 APPC team also in the queue for an OOM intro/demo Microsoft/Azure in the queue under https://jira.onap.org/browse/OOM-524 Amazon/EC2 in the queue as well under a support ticket started 2 weeks ago Current config – validated daily and kept up to date by developers above as well https://wiki.onap.org/display/DW/ONAP+on+Kubernetes#ONAPonKubernetes-QuickstartInstallation Last cross team blitz root page https://wiki.onap.org/display/DW/Vetted+vFirewall+Demo+-+Full+draft+how-to+for+F2F+and+ReadTheDocs Gary, Marco, Brian, thanks also for the feedback – we can simplify the setup and doc and address the intermittent healthcheck issues specific to SDNC (10%), SDC (8%) and MSO (4%) at the compenent level. /michael Filtered on failing Healthchecks http://kibana.onap.info:5601/app/kibana#/dashboard/AWAtvpS63NTXK5mX2kuS?_g=(refreshInterval:(display:Off,pause:!f,value:0),time:(from:now-24h,mode:quick,to:now))&_a=(description:'',filters:!(('$state':(store:appState),meta:(alias:!n,disabled:!f,field:healthcheck,index:AWAtYVuQYNh0ncCb5IdF,key:healthcheck,negate:!f,type:phrase,value:FAIL),script:(script:(inline:'boolean%20compare(Supplier%20s,%20def%20v)%20%7Breturn%20s.get()%20%3D%3D%20v;%7Dcompare(()%20-%3E%20%7B%20def%20msg%20%3D%20doc%5B!'message.keyword!'%5D.value;%0Aif%20(doc%5B!'message.keyword!'%5D.value%20!!%3D%20null)%20%7B%0Aif%20(doc%5B!'message.keyword!'%5D.value%20%3D~%20%2FHealth%20Check%2F)%20%7B%0A%20%20if%20(doc%5B!'message.keyword!'%5D.value%20%3D~%20%2FPASS%2F)%20%7B%20%0A%20%20%20%20return%20%22PASS%22;%0A%20%20%7D%0A%20%20else%20%7B%0A%20%20%20%20return%20%22FAIL%22;%0A%20%20%7D%0A%7D%0A%7D%0Areturn%20null;%20%7D,%20params.value);',lang:painless,params:(value:FAIL))))),options:(darkTheme:!f),panels:!((col:1,id:AWAts77k3NTXK5mX2kuM,panelIndex:1,row:1,size_x:8,size_y:3,type:visualization),(col:9,id:AWAtuTVI3NTXK5mX2kuP,panelIndex:2,row:1,size_x:4,size_y:3,type:visualization),(col:1,id:AWAtuBTY3NTXK5mX2kuO,panelIndex:3,row:7,size_x:6,size_y:3,type:visualization),(col:1,id:AWAttmqB3NTXK5mX2kuN,panelIndex:4,row:4,size_x:6,size_y:3,type:visualization),(col:7,id:AWAtvHtY3NTXK5mX2kuR,panelIndex:6,row:4,size_x:6,size_y:6,type:visualization)),query:(match_all:()),timeRestore:!f,title:'CD%20Health%20Check',uiState:(),viewMode:view) From: [email protected] [mailto:[email protected]] On Behalf Of Gary Wu Sent: Wednesday, January 3, 2018 13:16 To: PLATANIA, MARCO (MARCO) <[email protected]>; Alexis de Talhouët <[email protected]>; GILBERT, MAZIN E (MAZIN E) <[email protected]> Cc: onap-discuss <[email protected]> Subject: Re: [onap-discuss] [integration][oom] OOM readiness for Beijing release My experience with OOM (excluding DCAE) so far is that SDC fails to pass health check about half the time. When this happens, the best solution seems to be re-deploying the entire ONAP again, and if you’re lucky it will work. This appears to have been observed by others as well. The good thing is that we can do the re-deploy in about 10 minutes (excluding DCAE). First impressions: · The system is highly dependent in using exact versions of everything: docker, kubernetes, helm, rancher, etc. If anything is slightly off, things would break, and it would not be obvious exactly what was wrong. As a result, it makes the system feel fragile. · The SDC intermittent issue above makes the OOM deployments feel not fully stable/repeatable yet. · The OOM “how-to” documentation has almost too much information, covering multiple options/paths that sometimes overlap (e.g. where to install Rancher server vs agent, whether to use the cd.sh or manually perform individual steps). This made it hard for a newcomer to discern which steps need to be run next given which other choices were made earlier, and it was also hard to figure out if any mistakes were made performing some prior steps. I was not able to find any information on how to deploy DCAE via OOM; the most I got so far was that the DCAE controller container was able to bring up about half of the expected DCAE VMs, but not enough to be able to pass the DCAE health check. Thanks, Gary From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of PLATANIA, MARCO (MARCO) Sent: Wednesday, January 03, 2018 9:15 AM To: Alexis de Talhouët <[email protected]<mailto:[email protected]>>; GILBERT, MAZIN E (MAZIN E) <[email protected]<mailto:[email protected]>> Cc: onap-discuss <[email protected]<mailto:[email protected]>> Subject: Re: [onap-discuss] [integration][oom] OOM readiness for Beijing release I’ve been playing around with the OOM solution for a while and I was able to instantiate the vFW, vLB/vDNS, plus another dummy generic VNF that I created. I installed a minimal version of DCAE (only the collector and one CDAP container with the Threshold-crossing microservices) to run closed loop, waiting for the whole DCAE platform to be ready. I wasn’t able to run closed loop yet, perhaps due to out-of-sync configuration in my environment. I’m trying to fix this and see how far I can go with closed loop. Marco From: <[email protected]<mailto:[email protected]>> on behalf of Alexis de Talhouët <[email protected]<mailto:[email protected]>> Date: Wednesday, January 3, 2018 at 11:36 AM To: "GILBERT, MAZIN E (MAZIN E)" <[email protected]<mailto:[email protected]>> Cc: onap-discuss <[email protected]<mailto:[email protected]>> Subject: Re: [onap-discuss] [integration][oom] OOM readiness for Beijing release Mazin, So far, that I’m aware of, a few ppl from various company have tried OOM Amsterdam, and have successfully deployed vFWCL. If you want names and email, I guess I can find them for you. We’re currently testing vFWCL close loop with DCAE being deployed by OOM; I’d say it’s 80% done. Thanks, Alexis On Jan 3, 2018, at 11:21 AM, GILBERT, MAZIN E (MAZIN E) <[email protected]<mailto:[email protected]>> wrote: Thanks Roger. Have there been other groups who have managed to bring up Amsterdam with OOM (with and without DCAE)? Can you point me to any so I can understand their experience. mazin On Jan 3, 2018, at 11:15 AM, Roger Maitland <[email protected]<mailto:[email protected]>> wrote: Hi Helen, David is on vacation so I’ll answer - OOM is ready. The OOM team has been working with the Integration team and the entire ONAP community to create the amsterdam<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Doom.git-3Ba-3Dshortlog-3Bh-3Drefs_heads_amsterdam&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=_dlaJi5cUYGfdQpkrTvOLmwKf9nHldPQl5dmZYtz2iQ&s=uYM-V22L0V1EhonUacGlX4_i-MF4XdWNLtYWzReGYA4&e=> release of OOM which is now available. There is a continuous delivery system that deploys the master branch of all of the ONAP components with OOM – here<http://kibana.onap.info:5601/app/kibana#/dashboard/AWAtvpS63NTXK5mX2kuS?_g=(refreshInterval:(display:Off,pause:!f,value:0),time:(from:now-24h,mode:quick,to:now))&_a=(description:%27%27,filters:!(),options:(darkTheme:!f),panels:!((col:1,id:AWAts77k3NTXK5mX2kuM,panelIndex:1,row:1,size_x:8,size_y:> is the dashboard. As this system is effectively continuously evaluating ONAP health this should be very useful for the Integration team to quickly identify component submissions that result in a degradation. The initial version of DCAE support is under final testing. This version brings up the DCAE controller which then brings up the rest of the DCAE VMs. There is a discussion scheduled for tomorrow between the OOM and DCAE team on a more fully containerized solution. The OOM team is also working on deploying OpenStack DNS Designate to simply the deployment of OpenStack infrastructure required for DCAE. We’ll let the community know when this is ready. Cheers, Roger From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Yunxia Chen Sent: Tuesday, January 2, 2018 5:25 PM To: onap-discuss <[email protected]<mailto:[email protected]>>; Sauvageau, David <[email protected]<mailto:[email protected]>> Subject: [onap-discuss] [integration][oom] OOM readiness for Beijing release Hi, David, Happy new year and it was very nice to talk with you at Santa Clara. Is OOM ready for Integration team to take over to test the Beijing release, maybe start with Amsterdam project first? From last meeting, it seems have a little bit issue on DCAE, has it resolved yet? Regards, Helen Chen This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=_dlaJi5cUYGfdQpkrTvOLmwKf9nHldPQl5dmZYtz2iQ&s=EJl3g98o-LmIGfk4sjynukqHSJ3epLjqaYO4anfC954&e=> _______________________________________________ onap-discuss mailing list [email protected]<mailto:[email protected]> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=_dlaJi5cUYGfdQpkrTvOLmwKf9nHldPQl5dmZYtz2iQ&s=j7WSvxdz-fKgmH76NuG-x2cW3E_oZL4nU8OuXiW1ylM&e= _______________________________________________ onap-discuss mailing list [email protected]<mailto:[email protected]> https://lists.onap.org/mailman/listinfo/onap-discuss<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwQFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=R31H22kxjYwICQ8ZD3yEbIihWWgllI9uTVKv-rEmq_M&s=1xdaNYoF-XWCfc_fUVLiqQGdG44FeNm_001LZk7EDBE&e=> This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
