Hi all, As a reminder,
Next week’s meeting will be dedicated to the presentation by SP of their requirements for Dublin: 1. Bell Canada 2. Vodafone Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:[email protected]] From: Alla Goldner Sent: Wednesday, September 26, 2018 1:17 PM To: 'Alexis de Talhouët' <[email protected]>; [email protected]; [email protected] Subject: RE: Feed-back about features priority for Dublin Alexis, thanks a lot!!! This really helps to advance our dialog on Dublin requirements and priorities!!! We are starting a series of Usecase subcommittee meetings to discuss SP requirements and responses on questions raised by usecase subcommittee for Dublin proposals. The first one is on October 8 – so we will have on agenda: 1. Your (Bell Canada) requirements described below 2. Vodafone new use cases for Dublin support Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:[email protected]] From: Alexis de Talhouët [mailto:[email protected]] Sent: Wednesday, September 26, 2018 10:26 AM To: Alla Goldner <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: Re: Feed-back about features priority for Dublin Here are a few other topics that I forget to mentioned that we would love to see prioritized in Dublin: - support for the applications to be deployed in a geo-redundant fashion (either active active/ active passive, ...) - support and integration of PNDA within DCAE/CLAMP - support for database as a service. A lot of applications are using SQL or Postgres, maybe we could harmonized and have one cluster of each where application could own their dB. - implementation of a proper CI system providing daily feedback using the full robot suite (e.g. run distribution and instantiation) on the state of all our branches, whether release branches or master. Example of such CI has been implemented at various place, but would be good to see that integrated within ONAP CI system. This will allow to catch régression way earlier in the development cycle. Regards, Alexis On Sep 26, 2018, at 9:09 AM, Alexis de Talhouët <[email protected]<mailto:[email protected]>> wrote: Hello Alla, As discussed yesterday, a critical feature we’ve been looking for is the ability to enable self service of ONAP by our operational teams. With this in mind, during the Casablanca timeframe, Controller Design Studio has emerged . It’s goal is to create a common platform to all controller providing design capability to define controller blueprint, e.g. the WHAT, and data dictionaries, e.g. the HOW. The blueprint is using a JSON TOSCA based representation. it’s leaving under CCSDK, and will be harmonize with APPC CDT. This initiative is well documented here https://wiki.onap.org/plugins/servlet/mobile?contentId=35523521#content/view/35523521 In order to used the self serve framework, a few new microservices has arised in the Casablanca timeframe. Our deliveries in Casablanca is to augment current vFW assignent orchestration use case to enable name generation at VNF and VF-MODULE level using policy based definition, and to enable auto-assignment of ip addresses within defined pools in an ipam system (we use netbox). The enablement of this feature in Casablanca is permitted thanks to new SO building block, and SDNC generic-resource-api DGs. There is still a lot of work to do in Dublin and sub-sequent release to properly integrate this within CCSDK and SDC and to be more feature complete. The work items are being listed here: https://wiki.onap.org/pages/viewpage.action?pageId=41422551 Finally, for those interested, we had a few deep dive sessions in all the components comprising this new feature, the recording can be find here: https://wiki.onap.org/display/DW/ONAP+Controller+Design+Studio+Working+Session Another feature that will be valuable for us would be to have TOSCA based orchestration at the SO layer. Regards, Alexis 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> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#3829): https://lists.onap.org/g/onap-tsc/message/3829 Mute This Topic: https://lists.onap.org/mt/26747390/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
