Re: [onap-tsc] Seed code for Service Orchestrator

2017-05-11 Thread eric.debeau 
+1

De : Ed Warnicke [mailto:hagb...@gmail.com]
Envoyé : jeudi 11 mai 2017 22:17
À : ROSE, DANIEL V
Cc : SPATSCHECK, OLIVER; DEBEAU Eric IMT/OLN; dewa...@gigaspaces.com; 
onap-tsc@lists.onap.org
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 
<dr6...@att.com<mailto:dr6...@att.com>> wrote:
There has been a ton of change on the page in the last day: 
https://wiki.onap.org/pages/diffpagesbyversion.action?pageId=4719246=29=6

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

-Original Message-
From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org>]
 On Behalf Of SPATSCHECK, OLIVER
Sent: Thursday, May 11, 2017 4:05 PM
To: eric.deb...@orange.com<mailto:eric.deb...@orange.com>; 
dewa...@gigaspaces.com<mailto:dewa...@gigaspaces.com>
Cc: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-tsc] Seed code for Service Orchestrator

*** Security Advisory: This Message Originated Outside of AT ***.
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, 
> eric.deb...@orange.com<mailto:eric.deb...@orange.com> 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
> ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4=yopWEEan7upXoI1z2e3hU3o52mzgW69H-rB7ZIT8-A8=r3tAPP-TO6TFW9dliuNeUQRkuweOwDof8ZXXYNxy8nw=

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=2wwdGZ3YcpSivQ2Kio028A=P3ocIvjpt_xeLNXVAxRECvAWNuMr4HDtz-qc9fROO9A=e4Ns63-VStxhnMGdv7vWHVfxhjlPO8z9gu3k3E6shes=
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
https://lists.onap.org/mailman/listinfo/onap-tsc


_

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 confiden

Re: [onap-tsc] Seed code for Service Orchestrator

2017-05-11 Thread Ed Warnicke 
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 <dr6...@att.com> 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=6
>
> 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
>
> -Original Message-
> From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-bounces@
> lists.onap.org] On Behalf Of SPATSCHECK, OLIVER
> Sent: Thursday, May 11, 2017 4:05 PM
> To: eric.deb...@orange.com; dewa...@gigaspaces.com
> Cc: onap-tsc@lists.onap.org
> Subject: Re: [onap-tsc] Seed code for Service Orchestrator
>
> *** Security Advisory: This Message Originated Outside of AT ***.
> 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, eric.deb...@orange.com 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
> > ONAP-TSC@lists.onap.org
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.
> onap.org_mailman_listinfo_onap-2Dtsc=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=
> 3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4=
> yopWEEan7upXoI1z2e3hU3o52mzgW69H-rB7ZIT8-A8=r3tAPP-
> TO6TFW9dliuNeUQRkuweOwDof8ZXXYNxy8nw=
>
> ___
> ONAP-TSC mailing list
> ONAP-TSC@lists.onap.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.
> onap.org_mailman_listinfo_onap-2Dtsc=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=
> 2wwdGZ3YcpSivQ2Kio028A=P3ocIvjpt_xeLNXVAxRECvAWNuMr4HDtz-
> qc9fROO9A=e4Ns63-VStxhnMGdv7vWHVfxhjlPO8z9gu3k3E6shes=
> ___
> ONAP-TSC mailing list
> ONAP-TSC@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-tsc
>
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Seed code for Service Orchestrator

2017-05-11 Thread ROSE, DANIEL V 
There has been a ton of change on the page in the last day: 
https://wiki.onap.org/pages/diffpagesbyversion.action?pageId=4719246=29=6

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

-Original Message-
From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of SPATSCHECK, OLIVER
Sent: Thursday, May 11, 2017 4:05 PM
To: eric.deb...@orange.com; dewa...@gigaspaces.com
Cc: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Seed code for Service Orchestrator

*** Security Advisory: This Message Originated Outside of AT ***.
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, eric.deb...@orange.com 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
> ONAP-TSC@lists.onap.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4=yopWEEan7upXoI1z2e3hU3o52mzgW69H-rB7ZIT8-A8=r3tAPP-TO6TFW9dliuNeUQRkuweOwDof8ZXXYNxy8nw=

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=2wwdGZ3YcpSivQ2Kio028A=P3ocIvjpt_xeLNXVAxRECvAWNuMr4HDtz-qc9fROO9A=e4Ns63-VStxhnMGdv7vWHVfxhjlPO8z9gu3k3E6shes=
 
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Seed code for Service Orchestrator

2017-05-11 Thread SPATSCHECK, OLIVER (OLIVER) 

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, eric.deb...@orange.com 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
> ONAP-TSC@lists.onap.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4=yopWEEan7upXoI1z2e3hU3o52mzgW69H-rB7ZIT8-A8=r3tAPP-TO6TFW9dliuNeUQRkuweOwDof8ZXXYNxy8nw=

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Seed code for Service Orchestrator

2017-05-11 Thread jamil.chawki 
Hello
I can't understand how projects editing are managed, modifications are 
introduced in SO project without agreement and not aligned with the what were 
discussed and agreed last week.

Phil,  Mazin cloud you clarify the situation ?
Regards
Jamil

Le 11 mai 2017 à 21:48, "eric.deb...@orange.com" 
> a écrit :

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
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

_

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
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Seed code for Service Orchestrator

2017-05-11 Thread eric.debeau 
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
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc