Hi, Chris, I hope it could be decide asap since we don’t have enough resource to work on both solution. From this week, Integration projects and other projects already started the pairing / integration testing in Integration lab: we really need a tool which is working for our test, right now, we are using heat template.
Ideally, I hope that we have both OOM and Heat work before Amsterdam release. I know OOM team works very hard to meet Amsterdam date: especially last two weeks, I was with them and saw how hard they are working and how helpful they are (especially Mike Elliott). But even from yesterday’s meeting I had with few projects, which declared finished the integration with OOM, by few minutes’ code level review, we found that they still have quick some bugs, one of the projects missed two docker images and other one has duplicated entries. Regards, Helen Chen From: <onap-tsc-boun...@lists.onap.org> on behalf of "Christopher Donley (Chris)" <christopher.don...@huawei.com> Date: Wednesday, September 20, 2017 at 1:49 PM To: Roger Maitland <roger.maitl...@amdocs.com>, Eric Debeau <eric.deb...@orange.com>, onap-tsc <onap-tsc@lists.onap.org> Subject: Re: [onap-tsc] [tsc]Vote: ONAP Deployment Proposal for Amsterdam Release By when do we need to make this decision? I thought we said we’d wait until the code freeze next week to see how much progress we’ve made. Chris From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Roger Maitland Sent: Wednesday, September 20, 2017 1:13 PM To: eric.deb...@orange.com; onap-tsc@lists.onap.org Subject: Re: [onap-tsc] [tsc]Vote: ONAP Deployment Proposal for Amsterdam Release I’ll add to this conversation from the OOM team’s point of view. The OOM team is continuing with the more efficient Kubernetes deployment option for ONAP and at this point have on-boarded all projects except for DCAE Gen 2, Usecase UI (both of which are in progress) and VFC (which is under review in gerrit). OOM is deployed in the Integration lab where we will continue to validate the firewall use case to prove equivalency with the VM deployment option. OOM provides many benefits including handling interproject startup dependencies, floating IP addresses, coexisting instances of ONAP, all while using the provided hardware resources as efficiently as possible. We believe the community will find OOM very useful when working with ONAP but we understand there is a small learning curve. Roger Maitland OOM Project From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of eric.deb...@orange.com<mailto:eric.deb...@orange.com> Sent: Wednesday, September 20, 2017 3:26 PM To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> Subject: [onap-tsc] [tsc]Vote: ONAP Deployment Proposal for Amsterdam Release Hello We agree that Heat template for OpenEcomp was first designed to run on Rackspace environment. However, the Heat template evolved to remove the Rackspace dependencies and I believe that the various tests we can produce on various OpenStack solutions in the community should eliminate the bugs as much as possible. We must consolidate at least one solution working for Amsterdam Release and I agree with Jason that is important to make ONAP easy to deploy and we must put some efforts for the installer documentation and the associated test cases to validate that the installation is OK. Regards Eric _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. 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-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
