Excellent! And saves an edit to the diagram :) From: Kang Xi [mailto:kang...@huawei.com] Sent: Monday, October 09, 2017 5:45 PM To: Yoav Kluger <yoav.klu...@amdocs.com>; onap-discuss <onap-discuss@lists.onap.org> Subject: RE: vCPE closed loop testing session
Yoav, During the test session Brian said that appc now has this feature to query AAI to get vserver ID from vnf ID. So we will let appc do it. -------------------------------------------------- Regards, Kang From:Yoav Kluger To:Kang Xi,onap-discuss, Date:2017-10-09 17:28:09 Subject:RE: vCPE closed loop testing session Turns out I was not the last one editing this diagram, so I don't have the up-to-date source. Whoever has it - please either make the change or send me the link to the source of the diagram so I can make the change. Thanks, Yoav Kluger Amdocs Technology +1(201)912-7294 +972-54-4850278 [amdocs-a] From: Kang Xi [mailto:kang...@huawei.com] Sent: Thursday, October 05, 2017 6:03 PM To: Yoav Kluger <yoav.klu...@amdocs.com<mailto:yoav.klu...@amdocs.com>>; onap-discuss <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>> Subject: RE: vCPE closed loop testing session Yoav, Thanks for the info. Very important. -------------------------------------------------- Regards, Kang From:Yoav Kluger To:Kang Xi,onap-discuss, Date:2017-10-05 17:39:29 Subject:RE: vCPE closed loop testing session Kang, Just a small correction in steps 5 and 6 below: 5. Policy process the event from DCAE, queries AAI to obtain the vServer ID, and sends a "restart" event to APPC through DMaaP with the vServerID as a parameter 6. APPC captures the event from Policy, and restarts the VM according to the vServerID received from Policy We were initially going to have APPC query AAI to get the vServerID, but it then turned out that APPC would not be able to do this for R1 so Policy will do it as it does today in the vFW use case. Hopefully APPC is able to do the query in R2 so we will go back to how we wanted to do this originally, which is more "right". I think the wiki still has it the original way - I will update. Thanks, Yoav Kluger Amdocs Technology +1(201)912-7294 +972-54-4850278 [cid:image002.jpg@01D34126.A11C8580] -----Original Appointment----- From: Kang Xi [mailto:kang...@huawei.com] Sent: Thursday, October 05, 2017 3:58 PM To: onap-discuss Subject: [onap-discuss] vCPE closed loop testing session When: Friday, October 06, 2017 1:00 PM-4:00 PM (UTC-05:00) Eastern Time (US & Canada). Where: https://zoom.us/j/4466667777 Hi DCAE, CLAMP, Policy, APPC, AAI, Please join this session to kick off vCPE closed loop testing. The environment is in the community open lab. Marco has installed ONAP under integration project. Vijay has manually set up DCAE VES collector and TCA and has verified that they are working. We will create a vGMUX VM for this testing. What to be tested include the following: 1. Design and load policy rules t policy engine. Ideally this should be done by CLAMP. In case of problems, the workaround is to use Policy GUI. 2. Preload AAI with vCPE data. The purpose is to lookup vServer using vGMUX VNF ID. 3. vGMUX sends packet loss VES to DCAE VES collector 4. DCAE TCA sends an event to Policy through DMaaP 1. Policy process the event from DCAE and sends a "restart" event to APPC through DMaaP 1. APPC captures the event from Policy, extracts the VNF ID from the event, queries AAI to obtain the vServer ID, and then restarts the VM If you have not yet obtained access to the open lab, please open a jira ticket and assign it to Stephen Gooch to request one. Once you get your account, you can set up an OpenVPN connection to the lab and access all the resources there. Thanks, Kang << File: ATT00001.txt >> 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 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 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 onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
