Hi Maopeng ,Dewayne and All:
I have updated the SO project proposal to demonstrate both alternative
approaches likes following:
[cid:[email protected]]
Please review it and correct me.
Thank you .
Best wishes
Jinxin
***************************************************************************************
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**************************************************************************************
***************************************************************************************
This e-mail and its attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed above.
Any use of the information contained herein in any way (including, but not
limited to, total or partial disclosure, reproduction, or dissemination) by
persons other than the intended recipient(s) is prohibited. If you receive
this e-mail in error, please notify the sender by phone or email immediately
and delete it!
***************************************************************************************
From: [email protected] [mailto:[email protected]]
Sent: 2017年5月18日 9:20
To: Jinxin (Saw) <[email protected]>
Cc: [email protected]; [email protected]; [email protected];
[email protected]
Subject: 答复: 转发: [onap-tsc] 答复: Re: 答复: Service Orchestrator project proposal
Hi jinxin,Dewayne
I agree with the jinxin's advices to change the proposal.
As Mazine said in the other mail:
"The TSC committee and community will continue to provide project feedback
over the next 2 weeks.
So nothing is written in stone.", so TSC agrees that we can continue to
change the project proposal.
I think we should change the proposal ASAP and submit to the WIKI. Let the
TSC review it on this week TSC meeting.
Best Regards
Maopeng
原始邮件
发件人： ＜[email protected]＞;
收件人：张茂鹏10030173; ＜[email protected]＞; ＜[email protected]＞;
＜[email protected]＞; ＜[email protected]＞;
日 期 ：2017年05月17日 21:38
主 题 ：转发: [onap-tsc] 答复: Re: 答复: Service Orchestrator project proposal
Hi Dewayne ,Maopeng
If both options could be pursued in parallel，I think we should change the
proposal like following:
It is envisioned that initial Releases of this project would demonstrate both
alternative approaches.
For Alternative 1 approach:
• Demonstrate SO BPMN workflows interacting with an off-the-shelf TOSCA
Orchestrator to collectively drive orchestration behavior for at least an
instantiation use case
• Demonstrate rainy day handling
• Accomplish the above in a way that is demonstrably extensible to
support lifecycle operations such as Scale-In and Scale-Out.
For Alternative 2 approach:
• Demonstrate SO BPMN workflows to drive TOSCA-aware orchestration
behavior for VoLTE use case, dependency to VF-C.
• Support lifecycle operations such as Scale-In and Scale-Out.
What’s your opinion.
Best wishes
Jinxin
***************************************************************************************
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**************************************************************************************
***************************************************************************************
This e-mail and its attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed above.
Any use of the information contained herein in any way (including, but not
limited to, total or partial disclosure, reproduction, or dissemination) by
persons other than the intended recipient(s) is prohibited. If you receive
this e-mail in error, please notify the sender by phone or email immediately
and delete it!
***************************************************************************************
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of
[email protected]<mailto:[email protected]>
Sent: 2017年5月17日 9:11
To: [email protected]<mailto:[email protected]>
Cc: [email protected]<mailto:[email protected]>
Subject: [onap-tsc] 答复: Re: 答复: Service Orchestrator project proposal
Hi DeWayne,
Do you mean that this project proposal should support option 1 and option
2( integrated with VF-C)?
If it is ture, the project proposal should be changed.
Best Regards
Maopeng
原始邮件
发件人： ＜[email protected]＞;
收件人：张茂鹏10030173;
抄送人： ＜[email protected]＞;
日 期 ：2017年05月16日 23:11
主 题 ：Re: 答复: [onap-tsc] Service Orchestrator project proposal
Maopeng,
The rationale behind option 1 vs option 2 was based on participant input at
the time. As far as I know, the time has passed for new project proposals. I
suppose it is conceivable with enough committers that both options could be
pursued in parallel. The proposal is submitted however. Perhaps the TSC can
chime in.
DeWayne
On Mon, May 15, 2017 at 1:02 AM,
＜[email protected]<mailto:[email protected]>＞ wrote:
Hi DeWayne,
I am interested in and already committed to contributing to this project.
I am afraid that I am confused since there are two alternatives on the proposal
page, but it said in release 1 the project will only demonstrate option 1( Only
depend on App-C project)
Since we are interested in contributing option 2, I doubt it is still open for
discussion? Or shall we document it in a separate project proposal instead?
Best Regards
Maopeng
原始邮件
发件人： ＜[email protected]<mailto:[email protected]>＞;
收件人： ＜[email protected]<mailto:[email protected]>＞;
日 期 ：2017年05月15日 01:32
主 题 ：[onap-tsc] Service Orchestrator project proposal
ONAP TSC, We would like to formally propose the SO (Service Orchestrator)
project for ONAP.. The proposal wiki page, which includes details of the
project description, project scopes, and proposed repo names, can be found at:
https://wiki.onap.org/display/DW/Service+Orchestrator. The SO team consists
of representatives from Cloudify, AT&T, Huawei, China Mobile, Ericsson, Orange,
Amdocs, Nokia, and ZTE.
Thanks,
DeWayne Filppi
Director Solution Architecture
Gigaspaces/Cloudify
[email protected]<mailto:[email protected]>
714.512.1706<tel:(714)%20512-1706>
--
DeWayne Filppi, Director, Solutions Architect
[https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/-27020792c3e94269b883d9a828be029f56c08986b2ab208a46143b169592c35a.png]<http://cloudify.co>
________________________________
M: +17145121706
http://cloudify.co<http://cloudify..co/>
@dfilppi
[https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/2fb5e7413e7dbeee3e88676333b65c05237ec13d3512e4a63ebc1b5f85bfb917.png]<https://twitter.com/CloudifySource>
[https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/16b91ab7a91bb3a298f2a322640bebb3754357f93e9f20ff50d2c94bb82b1814.png]
<https://www.linkedin.com/company-beta/17918192/>
[https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/6f7421bc5b9a93a0649735bbc8589b200c678bf08af9d7e0cebf1b3cffcdac94.png]
<https://github.com/cloudify-cosmo>
[https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/4be4d1377f4c1afe70a25e78926b6aad4e0a4fb1d45a7727e31d5a807eb3aae7.png]
<https://www.youtube.com/cloudifysource>
_______________________________________________
ONAP-TSC mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-tsc
