Dear all, I have discussed this morning with Steve Smokowski (who is part of the SO project proposal). He confirmed that the MSO code base was discussed with Gil/Dewayne in terms of text and goals to be part of SO proposal. A follow-up will be performed today with Dewayne in order to remove any confusion from the current proposal
Hope it helps. Best regards Catherine From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, May 11, 2017 10:21 PM To: Ed Warnicke <[email protected]>; ROSE, DANIEL V <[email protected]> Cc: [email protected]; SPATSCHECK, OLIVER <[email protected]>; [email protected] Subject: Re: [onap-tsc] Seed code for Service Orchestrator +1 De : Ed Warnicke [mailto:[email protected]] Envoyé : jeudi 11 mai 2017 22:17 À : ROSE, DANIEL V Cc : SPATSCHECK, OLIVER; DEBEAU Eric IMT/OLN; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Objet : Re: [onap-tsc] Seed code for Service Orchestrator In many other communities, as a matter of social norm, not governance, if one is going to edit a project proposal, it is considered good manners to ask the originator of a proposal before editing it in a substantive way. Perhaps we should consider communicating this social norm withing the ONAP community to avoid confusion? Ed On Thu, May 11, 2017 at 4:11 PM, ROSE, DANIEL V <[email protected]<mailto:[email protected]>> wrote: There has been a ton of change on the page in the last day: https://wiki.onap.org/pages/diffpagesbyversion.action?pageId=4719246&selectedPageVersions=29&selectedPageVersions=6<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_diffpagesbyversion.action-3FpageId-3D4719246-26selectedPageVersions-3D29-26selectedPageVersions-3D6&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=c31OYuaPawMl_ySS_voXJQ&m=Ns-THEbADHEsmMva5OU8iIXAKfl3p9kuagqPCIua5Gk&s=1mW_3IrISOQPKV-T0c2n7OvjCSbvmjPPpj7-2eKNehk&e=> I hope everyone who needed to be involved has been involved because I didn't see much public discussion about this project on this mailing lists. Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308<tel:732-420-7308> -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of SPATSCHECK, OLIVER Sent: Thursday, May 11, 2017 4:05 PM To: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]> Subject: Re: [onap-tsc] Seed code for Service Orchestrator *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. 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]<mailto:[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]<mailto:[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]<mailto:[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=2wwdGZ3YcpSivQ2Kio028A&m=P3ocIvjpt_xeLNXVAxRECvAWNuMr4HDtz-qc9fROO9A&s=e4Ns63-VStxhnMGdv7vWHVfxhjlPO8z9gu3k3E6shes&e= _______________________________________________ ONAP-TSC mailing list [email protected]<mailto:[email protected]> https://lists.onap.org/mailman/listinfo/onap-tsc<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=c31OYuaPawMl_ySS_voXJQ&m=Ns-THEbADHEsmMva5OU8iIXAKfl3p9kuagqPCIua5Gk&s=noPDGY3AB2dh-HB70bGUImlaA4Hwq375fjzqzkqpEwU&e=> _________________________________________________________________________________________________________________________ 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://lists.onap.org/mailman/listinfo/onap-tsc
