Team, I posted to the VoLTE Use Case wiki (Drafts for discussion sub-page) an updated version of the PPT file that I quickly covered in today's call. It contains a proposal on how to support this near term need that we face together.
Here is the link: https://wiki.onap.org/display/DW/VoLTE+Drafts+for+discussion I intend that this proposal has an advantage of minimizing rework and misalignment of Release 1 and Release 2. Note the SO functionality in this proposal aligns with that which is being proposed in the vCPE Residential Broadband Use Case. You will note that in this PPT I have also proposed a "design time" approach that results in a "flat" VoLTE model in the Release 2 timeframe through "compile time nesting". Please do not conclude from this that I do not appreciate the business benefit of modeling in ONAP complex, multi-tiered services. I do appreciate that need, and I agree that ONAP needs to be able to support such complex, "n-tiered" services. In fact, I am proposing in this deck one way to accomplish such support, at least in the near term, by "flattening" the orchestration of such services. Please also do not conclude from this "flattening" proposal that I am pushing back on the concept of "upper level" run-time service orchestration flows recursively delegating to "lower level" service orchestration flows, in an "n-tier" construct. In fact, I find an attractive elegance to recursive flows like this. However, I am proposing to avoid such an "n-tier" flow approach in the near term because I do envision that such an implementation would add significant complexity to ONAP orchestration "rainy day handling", certainly in trouble-shooting. In addition, though I would like to see ONAP eventually support "rainy day handling" for such an "n-tier" orchestration architecture, I would prefer to first develop some underlying common "rainy day handling" infrastructure that each flow level can leverage. I foresee that such a task will take some significant design work. Because of that I propose the "compile time nesting" as a way to "flatten" the orchestration and to simplify this rainy day handling, at least in the near term "Release 2" timeframe. I look forward to other's comments and feedback. Gil Bullard AT&T -----Original Appointment----- From: denghui (L) [mailto:denghu...@huawei.com] Sent: Tuesday, August 01, 2017 11:44 AM To: denghui (L); onap-disc...@lists.onap.org; onap-tsc Subject: [onap-discuss] ONAP VoLTE SDC call When: Wednesday, August 02, 2017 10:00 PM-11:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/137904496 Hello all This is for discussion ONAP VoLTE SDC call. ONAP Meeting 5 is inviting you to a scheduled Zoom meeting. Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/137904496<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_url-3Fq-3Dhttps-253A-252F-252Fzoom.us-252Fj-252F137904496-26sa-3DD-26usd-3D2-26usg-3DAFQjCNHWLm-2DMNCNZh9JQ8TByZ7QBGA-5FnzQ&d=DwMFoQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=7myXm661_1A0qXYelqzRGcVtwAFpJWmehuKCEoQLzm8&m=bENeQZaD6ESl-_RBR2qvPdlRSSHOub4Ufe5UK7nnR4U&s=3RMGXLmyRbJCxBMXOvzjfi7uZiYzX-LBvnYwlpGjhPw&e=> Or iPhone one-tap (US Toll): +14086380968,137904496# or +16465588656,137904496# Or Telephone: Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll) Meeting ID: 137 904 496 International numbers available: https://zoom.us/zoomconference?m=mi-ad1sMLWlXByAKLio5vDnd9JYqUR_a<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_url-3Fq-3Dhttps-253A-252F-252Fzoom.us-252Fzoomconference-253Fm-253Dmi-2Dad1sMLWlXByAKLio5vDnd9JYqUR-5Fa-26sa-3DD-26usd-3D2-26usg-3DAFQjCNGUpQlMWM7Hx42afMT3U-2DkpQiPOMA&d=DwMFoQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=7myXm661_1A0qXYelqzRGcVtwAFpJWmehuKCEoQLzm8&m=bENeQZaD6ESl-_RBR2qvPdlRSSHOub4Ufe5UK7nnR4U&s=HD9t4B2h3p7NsXAFT2osOvYd0lzusPWuxRSS6rGYA4s&e=> Thanks a lot DENG Hui << File: ATT00001.txt >>
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
