+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
p.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
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
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
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,
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
