So am I. I thought in the charter we had agreed that the MSO code base would be used for this. Similar to the 3 legacy Open-O components.
Was there any discussion on this anywhere? Thx Oliver > On May 11, 2017, at 3:48 PM EDT, [email protected] wrote: > > Hello > > I am surprised to discover that open-o/gso is considered as the seed code for > the Service Orchestrator. > > As far as I know, we never decided such choice during the discussions last > week and it should be a TSC decision. > > Regards > > Eric > _________________________________________________________________________________________________________________________ > > 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. > > _______________________________________________ > ONAP-TSC mailing list > [email protected] > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4&m=yopWEEan7upXoI1z2e3hU3o52mzgW69H-rB7ZIT8-A8&s=r3tAPP-TO6TFW9dliuNeUQRkuweOwDof8ZXXYNxy8nw&e= _______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
