Hi Helen, Thanks to the help I was given from folks this morning, I have completed the VFWCL testing, and everything is working fine. I’m going to re-do it from scratch, and then cover other use cases. But I’m confident all should be tested/validated by end of next week. I’m also re-freshing two wiki pages, one to deploy OOM on Kubernetes, on Rancher, in OpenStack: https://wiki.onap.org/display/DW/ONAP+on+Kubernetes+on+Rancher+in+OpenStack <https://wiki.onap.org/display/DW/ONAP+on+Kubernetes+on+Rancher+in+OpenStack> and one to run the vFW demo: https://wiki.onap.org/display/DW/vFWCL+instantiation%2C+testing%2C+and+debuging <https://wiki.onap.org/display/DW/vFWCL+instantiation,+testing,+and+debuging>
They both can look redundant with some other pages, but I trust they are very straightforward to follow (to David’s point and others). Thanks, Alexis > On Jan 3, 2018, at 3:08 PM, Yunxia Chen <helen.c...@huawei.com> wrote: > > Hi, Alexis, > Sorry for the push. Could I get a timeframe for that? I would like the team > to get hands on experience and based on that, making decision whether we’d > like to keep both OOM and Heat for Beijing. My concern is how quick OOM could > keep up with those new projects? (We are again need to make hard decision, > keep both will need more resource for us). > > Regards, > > Helen Chen > > From: <onap-discuss-boun...@lists.onap.org> on behalf of Alexis de Talhouët > <adetalhoue...@gmail.com> > Date: Wednesday, January 3, 2018 at 11:42 AM > To: "FREEMAN, BRIAN D" <bf1...@att.com> > Cc: "GILBERT, MAZIN E (MAZIN E)" <ma...@research.att.com>, onap-discuss > <onap-discuss@lists.onap.org> > Subject: Re: [onap-discuss] [integration][oom] OOM readiness for Beijing > release > > Brian, > > Yes, it does sound reasonable. That being said, I’m very much involved in > finishing DCAE support in OOM. Once done, along with the testing the various > use cases, I’ll sync up with Michael to provide a clear, straightforward > documentation, both for setup and usage, providing tips and ways to debug. > > Thanks, > Alexis > > > On Jan 3, 2018, at 2:15 PM, FREEMAN, BRIAN D <bf1...@att.com > <mailto:bf1...@att.com>> wrote: > > Gary, > > I think Michael was trying to be complete in describing options with a plan > to do a cleaned up documentation after it was working and scripted up. > Perhaps its time to formally start a new page with the final recommended – > single path and scripted install (I agree that it was daunting at the start > to find the latest parts/procedure which was much simpler than the first > procedure) > > Michael/Alexis – is that reasonable ? > Brian > > > From: onap-discuss-boun...@lists.onap.org > <mailto:onap-discuss-boun...@lists.onap.org> > [mailto:onap-discuss-boun...@lists.onap.org > <mailto:onap-discuss-boun...@lists.onap.org>] On Behalf Of Gary Wu > Sent: Wednesday, January 03, 2018 1:16 PM > To: PLATANIA, MARCO <plata...@research.att.com > <mailto:plata...@research.att.com>>; Alexis de Talhouët > <adetalhoue...@gmail.com <mailto:adetalhoue...@gmail.com>>; GILBERT, MAZIN E > <ma...@research.att.com <mailto:ma...@research.att.com>> > Cc: onap-discuss <onap-discuss@lists.onap.org > <mailto:onap-discuss@lists.onap.org>> > 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: onap-discuss-boun...@lists.onap.org > <mailto:onap-discuss-boun...@lists.onap.org> > [mailto:onap-discuss-boun...@lists.onap.org > <mailto:onap-discuss-boun...@lists.onap.org>] On Behalf Of PLATANIA, MARCO > (MARCO) > Sent: Wednesday, January 03, 2018 9:15 AM > To: Alexis de Talhouët <adetalhoue...@gmail.com > <mailto:adetalhoue...@gmail.com>>; GILBERT, MAZIN E (MAZIN E) > <ma...@research.att.com <mailto:ma...@research.att.com>> > Cc: onap-discuss <onap-discuss@lists.onap.org > <mailto:onap-discuss@lists.onap.org>> > 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: <onap-discuss-boun...@lists.onap.org > <mailto:onap-discuss-boun...@lists.onap.org>> on behalf of Alexis de Talhouët > <adetalhoue...@gmail.com <mailto:adetalhoue...@gmail.com>> > Date: Wednesday, January 3, 2018 at 11:36 AM > To: "GILBERT, MAZIN E (MAZIN E)" <ma...@research.att.com > <mailto:ma...@research.att.com>> > Cc: onap-discuss <onap-discuss@lists.onap.org > <mailto:onap-discuss@lists.onap.org>> > 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) > <ma...@research.att.com <mailto:ma...@research.att.com>> 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 <roger.maitl...@amdocs.com > <mailto:roger.maitl...@amdocs.com>> 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 > <https://urldefense.proofpoint.com/v2/url?u=http-3A__kibana.onap.info-3A5601_app_kibana-23_dashboard_AWAtvpS63NTXK5mX2kuS-3F-5Fg-3D-28refreshInterval-3A-28display-3AOff-2Cpause-3A-21f-2Cvalue-3A0-29-2Ctime-3A-28from-3Anow-2D24h-2Cmode-3Aquick-2Cto-3Anow-29-29-26-5Fa-3D-28description-3A-2527-2527-2Cfilters-3A-21-28-29-2Coptions-3A-28darkTheme-3A-21f-29-2Cpanels-3A-21-28-28col-3A1-2Cid-3AAWAts77k3NTXK5mX2kuM-2CpanelIndex-3A1-2Crow-3A1-2Csize-5Fx-3A8-2Csize-5Fy-3A&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=TEGneiYu3X69Tbakkf-0jbhukaSEN5O-Dj-rwTm4eXY&s=HXzlpENhYHSnNMtU61IUybmlPUBxj2VxcRYHbRcCRJw&e=> > 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: onap-discuss-boun...@lists.onap.org > <mailto:onap-discuss-boun...@lists.onap.org> > [mailto:onap-discuss-boun...@lists.onap.org > <mailto:onap-discuss-boun...@lists.onap.org>] On Behalf Of Yunxia Chen > Sent: Tuesday, January 2, 2018 5:25 PM > To: onap-discuss <onap-discuss@lists.onap.org > <mailto:onap-discuss@lists.onap.org>>; Sauvageau, David > <david.sauvag...@bell.ca <mailto:david.sauvag...@bell.ca>> > 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 > onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org> > 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= > > <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 > onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org> > 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=> > >
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
