Good news Robert! How looks the notification procedure for service order updates / completions? Are they as well in scope of the service resolver? (like in the standard NBI?)
BR Marc Von: [email protected] <[email protected]> Im Auftrag von Srini Gesendet: Mittwoch, 18. September 2019 17:03 An: [email protected]; [email protected]; [email protected] Betreff: Re: [onap-discuss] E2E Service Orchestration by ONAP This concept looks very good. I went through readme document in your gitlab source code. I guess ‘Service resolver’ is like Multi-Domain orchestrator. By doing as its own set of Micro-services, central deployment (Multi-Domain Orchestrator) can be simple and does not need to have rest of ONAP. ONAP, as it exists today, can be implementation for domain orchestrators. I know that it is new and assuming that it is accepted in the wider community, Telstra domain orchestrator need to register to ‘Service resolver’ and also use service resolver to add its services. Love to know more details about ‘Service resolver’. Are you planning to present this in ONAP architecture or DDF any time soon? Thanks Srini From: [email protected]<mailto:[email protected]> [mailto:[email protected]] Sent: Wednesday, September 18, 2019 4:51 AM To: [email protected]<mailto:[email protected]>; Addepalli, Srinivasa R <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: RE: [onap-discuss] E2E Service Orchestration by ONAP Hello Service Resolver is implementing the option 1 It is a fresh new feature we added last week. The process : * You define a service (CFS) composed with services (RFS). * In each RFS definition you have an information about the “orchestrator” (= an ONAP platform for example) that will be able to instantiate the RFS * Service Resolver is then able to receive an order for the CFS and to transmit the RFS instantiation orders to the various “orchestrators” https://gitlab.com/Orange-OpenSource/lfn/onap/service-resolver Best regards [Logo Orange]<http://www.orange.com/> René Robert «Open and Smart solutions for autOmating Network Services» ORANGE/IMT/OLN/CNC/NARA/OSONS Fixe : +33 2 96 07 39 29 <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2096%2007%2039%2029> Mobile : +33 6 74 78 68 43 <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2074%2078%2068%2043> [email protected]<mailto:[email protected]> De : [email protected]<mailto:[email protected]> [mailto:[email protected]] De la part de Srini Envoyé : mardi 17 septembre 2019 18:18 À : [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Objet : Re: [onap-discuss] E2E Service Orchestration by ONAP Hi Atif, As far as I know there are no principles defined. But, we did some study on how to integrate domain orchestrators such as “Multi K8S Cluster orchestration” along with other domain orchestrators and also resource orchestrators. There are two ways go about this. 1. A high level service with nested services where nested services handled by various domain orchestrators. 2. A service with resources where resources are handled by domain orchestrators. 3. Of course, combination of both. If you want domain orchestrator to be called from SO/MC, then (2) approach is needed in my view. On (1), I don’t know whether there are any examples. On (2), there are three examples - Multi-Cluster (k8s) orchestration (WIP), Azure Orchestration and AWS Orchestration (AWS is WIP ) In all three examples of (2), each VNF (VF) resource is treated as the self-contained entity. Within Azure/AWS/Multi-Cluster orchestration, they take care of deploying components of VNF in various locations supported by that domain. For example, Azure has lot of sites, but these are not known to the ONAP. Any VNF placement in Azure sties is the job of Azure domain orchestrator. In “Multi-Cluster Orchestration” too, our thinking is similar to Azure and AWS, where it acts domain orchestrator and takes care of placement decisions for workloads within VNF/VF. And let the ONAP (SO/OOF) do the placement decisions across VNFs (in a service). I hope it helps and request others to comment. Thanks Srini From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Husain, Atif Sent: Monday, September 16, 2019 11:03 PM To: [email protected]<mailto:[email protected]> Subject: [onap-discuss] E2E Service Orchestration by ONAP Hi, Are there any principles defined for ONAP related to its use for E2E Service Orchestration across multiple domains? Regards, Atif _________________________________________________________________________________________________________________________ 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. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#19000): https://lists.onap.org/g/onap-discuss/message/19000 Mute This Topic: https://lists.onap.org/mt/34173460/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
