Thanks, Kang. As discussed, Here's list of things we need to discuss and address:
* placementDemands should include the vgMuxInfra and vG * BRG should be removed from the placementDemands since it is a PNF and homing doesn't really make sense given its location is already fixed. * the licenceDemand section should be removed (potentially) since we aren't really doing any license optimization in R2. Also, the testing would involve two incremental steps: Step 1. Test the basic Homing workflow for vCPE with the air-distance and colocation constraints ( https://wiki.onap.org/display/DW/HAS+%28R2%29+Beijing+Release+planning). Step 2. Add the HPA and MultiCloud capacity check policies, and test with the functional test cases. The first step would ease us into the workflow replacing the SNIRO emulator, while step 2 would test all the functional features we support in R2. Thanks, Shankar. On Mon, May 21, 2018 at 11:24 AM Kang Xi <[email protected]> wrote: > Shankar, > > > > Please get the SNIRO request and response here: > https://wiki.onap.org/download/attachments/16008042/sniro_request.json?version=1&modificationDate=1526916059788&api=v2 > > > https://wiki.onap.org/download/attachments/16008042/sniro_response.json?version=1&modificationDate=1526916059957&api=v2 > > > > Marcus, > > > > I’ll set up a short meeting later today so that Shankar, you, and me can > sync up on the test. Thanks. > > > > Regards, > > Kang > > > > *From:* Shankaranarayanan P N [mailto:[email protected]] > *Sent:* Monday, May 21, 2018 10:16 > *To:* Yunxia Chen <[email protected]> > *Cc:* Gildas Lanilis <[email protected]>; PATEL, ANKITKUMAR N > (ANKITKUMAR N) <[email protected]>; [email protected]; LEFEVRE, > CATHERINE <[email protected]>; FREEMAN, BRIAN D <[email protected]>; > [email protected]; [email protected]; Kang Xi < > [email protected]> > *Subject:* Re: OOF integration testing > > > > Thanks, Helen. > > > > Kang, Please let me know when we could discuss about the schedule and > priority for this testing. > > > > Thanks, > > Shankar. > > > > On Mon, May 21, 2018 at 1:04 AM Yunxia Chen <[email protected]> wrote: > > Hi, Shankar, > > Thanks for the update. Please discuss with Kang, added on this maillist, > on schedule and priority. > > > > Regards, > > > > Helen Chen > > > > *From: *Shankaranarayanan P N <[email protected]> > *Date: *Friday, May 18, 2018 at 10:21 AM > *To: *Helen Chen 00725961 <[email protected]>, Gildas Lanilis < > [email protected]>, "PATEL, ANKITKUMAR N (ANKITKUMAR N)" < > [email protected]>, "[email protected]" <[email protected]>, > "LEFEVRE, CATHERINE" <[email protected]>, "FREEMAN, BRIAN D" < > [email protected]>, "[email protected]" <[email protected]>, > onap-discuss <[email protected]> > *Subject: *OOF integration testing > > > > Hi Helen, Gildas, > > > > Following up on our earlier meeting regarding the integration testing, I > wanted to reach out and provide an update on the progress here as you > requested. > > > > We have completed all the pairwise testing with our downstream > dependencies (AAI, MultiCloud, Policy), and expect to complete the > Northbound testing with SO in a short while. In order to simultaneously > progress alongside the integration testing efforts, we have been primarily > using the vCPE workflows for our pairwise testing. > > > > Since OOF is called by SO for homing in the vCPEResCust instantiation > workflow, I wanted to check if the following plan for the testing would > work: > > > > 1. Test the basic Homing workflow for vCPE with minimal constraints ( > https://wiki.onap.org/display/DW/HAS+%28R2%29+Beijing+Release+planning). > This would, in effect, replace the SNIRO emulator stub in R1 flows with OOF > homing workflow. > > 2. Add the HPA and MultiCloud capacity check policies, and test with the > functional test cases. > > > > This way, we can start off with an initial but meaningful test and make > progress incrementally by adding more complex policies. Please let us know > if this sounds reasonable. > > > > Thank you so much for your help with the testing efforts ! > > > > Thanks, > > Shankar. > > > > > > > >
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
