https://wiki.onap.org/display/DW/SO+%3A+How+it+works
De : onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] De la part de David Perez Envoyé : vendredi 27 juillet 2018 09:54 À : onap-discuss@lists.onap.org; ss8...@att.com Cc : ROBERT René IMT/OLN Objet : Re: [onap-discuss][SO] How it works (to be completed) Hi René, great idea, this is really helpful. If not done yet, I would suggest to add this text to the wiki so that it doesn’t get lost in the mailing list. Could you please also indicate the difference between model_uuid and model_invariant_uuid when describing the entries to be inserted in SO DB? Something like model_uuid: versioned identifier of the service model (this uuid is changed for every major version of the service) model_invariant_uuid: constant identifier of the service model Ref: https://wiki.onap.org/display/DW/SDC+Data+model @Steve: The BPMN workflows added via REST API are immediately available? no SO rebuild is required? Thanks, David -- David Pérez Caparrós Senior Innovation Engineer Swisscom (Switzerland) david.perezcapar...@swisscom.com<mailto:david.perezcapar...@swisscom.com> On 25 Jul 2018, at 16:09, Steve Smokowski <ss8...@att.com<mailto:ss8...@att.com>> wrote: How to add a new BPMN for a service ? BPMN can be deployed over a REST API, we are investigating exposing this in Casablanca Thanks -Steve From: <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>> on behalf of Rene Robert <rene.rob...@orange.com<mailto:rene.rob...@orange.com>> Reply-To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>, "rene.rob...@orange.com<mailto:rene.rob...@orange.com>" <rene.rob...@orange.com<mailto:rene.rob...@orange.com>> Date: Wednesday, July 25, 2018 at 9:36 AM To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>> Subject: [onap-discuss][SO] How it works (to be completed) Hello all, In order to enhance ONAP documentation, I propose you to complete with me that short description around SO and Workflow ************************************************************************************************ What happens when ONAP SDC is distributing service model to ONAP SO ? Informations are updated in the SO MariaDB database called “mso_catalog”, and especially in the table called “service” A new entry is inserted in that table for fields : MODEL_UUID (= UUID in SDC or Tosca file), MODEL_NAME (= name in SDC or Tosca file), MODEL_INVARIANT_UUID (= invariantUUID in SDC or Tosca file) SERVICE_CATEGORY (= category in SDC or Tosca file) in the SO MariaDB database called “mso_catalog”, there is also a table called “service_recipe” but that table is not modified by SDC distribution process. What happens when trying to create or delete a service instance based on a service model ? SO provides two northbound Rest API : The “serviceInstances” API : http://mso.api.simpledemo.onap.org:8080/ecomp/mso/infra/serviceInstances/v6<https://urldefense.proofpoint.com/v2/url?u=https-3A__plazza.orange.com_external-2Dlink.jspa-3Furl-3Dhttp-253A-252F-252Fmso.api.simpledemo.onap.org-253A8080-252Fecomp-252Fmso-252Finfra-252FserviceInstances-252Fv6&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=shs6nPzThSiGJml9VXN0Eg&m=nLcrgT9T_zxsaFACBCgWsY7XlzIWmZBnIJhnE5UHVVg&s=Wa3C_oelAGyZBO_6D8mDuRoSowyOzh0GiN49kpIKhZA&e=> This API is used by VID and NBI components The “e2eServiceInstances” API : http://mso.api.simpledemo.onap.org:8080/ecomp/mso/infra/e2eServiceInstances/v3<https://urldefense.proofpoint.com/v2/url?u=https-3A__plazza.orange.com_external-2Dlink.jspa-3Furl-3Dhttp-253A-252F-252Fmso.api.simpledemo.onap.org-253A8080-252Fecomp-252Fmso-252Finfra-252Fe2eServiceInstances-252Fv3&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=shs6nPzThSiGJml9VXN0Eg&m=nLcrgT9T_zxsaFACBCgWsY7XlzIWmZBnIJhnE5UHVVg&s=ZjW3_6o_BEFQYU950Wdey1lXQTlt-ZXImXRN80iaFBw&e=> This API is used by UUI component but seems dedicated to voLTE usecase (some hard coding values...) When SO receive the Rest API message, the API Handler (an SO module) will check in the SO MariaDB, in the database called “mso_catalog” and in the table called “service_recipe” if there is an entry that match the serviceModelUUID contained in the request body (= UUID coming from SDC or TOSCA file). If there is an entry, then, the URI of the Orchestration BPMN is indicated in the table. If no entry, then, the default Orchestration BPMN URI is selected. Default Orchestration BPMN URI is different if using “serviceInstances” API or “e2eServiceInstances” API. For a POST for a “serviceInstances” API, the default BPMN URI is : /mso/async/services/CreateGenericALaCarteServiceInstance For a POST for a “e2eServiceInstances” API , the default BPMN URI is : /mso/async/services/CreateCustomE2EServiceInstance TO BE COMPLETED : interactions between API Handler and Camunda engine to effectively launch the BPMN ? see mso-api-handlers/mso-api-handler-infra/src/main/java/org/openecomp/mso/apihandlerinfra/ServiceInstances.java What to do if I want to use a specific BPMN for a service ? Analysing the ONAP vCPE use-case, it can be noticed that a new entry is inserted, by an init script, in the “service_recipe” table with the vCPE service UUID and the specific BPMN URI : /mso/async/services/CreateVcpeResCustService How to add a new BPMN for a service ? All BPMN are already present in the SO when installing ONAP. BPMN are part of the source code. Even for vCPE use-case, the BPMNs are in the SO source code. Not sure that it is possible to upload a new BPMN in a running SO without building a new jar/war file of the entire SO module, and rebuilding the docker container. TO BE COMPLETED <image001.gif><https://urldefense.proofpoint.com/v2/url?u=http-3A__www.orange.com_&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=shs6nPzThSiGJml9VXN0Eg&m=nLcrgT9T_zxsaFACBCgWsY7XlzIWmZBnIJhnE5UHVVg&s=NR9dluyDbNCpkWL1ur9XeE8rUMmxMo6_6YNmEiBWL-Y&e=> René Robert Fixe : +33 2 96 07 39 29 <https://urldefense.proofpoint.com/v2/url?u=https-3A__monsi.sso.francetelecom.fr_index.asp-3Ftarget-3Dhttp-253A-252F-252Fclicvoice.sso.francetelecom.fr-252FClicvoiceV2-252FToolBar.do-253Faction-253Ddefault-2526rootservice-253DSIGNATURE-2526to-253D-2B33-25202-252096-252007-252039-252029&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=shs6nPzThSiGJml9VXN0Eg&m=nLcrgT9T_zxsaFACBCgWsY7XlzIWmZBnIJhnE5UHVVg&s=420NlCuv7ujneY3HF9mDfz7KRrw4wqbUuppXo2YLDyY&e=> Mobile : +33 6 74 78 68 43 <https://urldefense.proofpoint.com/v2/url?u=https-3A__monsi.sso.francetelecom.fr_index.asp-3Ftarget-3Dhttp-253A-252F-252Fclicvoice.sso.francetelecom.fr-252FClicvoiceV2-252FToolBar.do-253Faction-253Ddefault-2526rootservice-253DSIGNATURE-2526to-253D-2B33-25206-252074-252078-252068-252043&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=shs6nPzThSiGJml9VXN0Eg&m=nLcrgT9T_zxsaFACBCgWsY7XlzIWmZBnIJhnE5UHVVg&s=R33-SqK9jz1SOFKecK1V-uKufTLfPo_Bc7NAMrnV4hE&e=> rene.rob...@orange.com<mailto:rene.rob...@orange.com> _________________________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________________________ 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 (#11480): https://lists.onap.org/g/onap-discuss/message/11480 Mute This Topic: https://lists.onap.org/mt/23812724/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-