Hi Zahi
The meeting time may conflict with the virtual development meeting.
IMHO, I think both the design-time and runtime are important.
We can talk the requirement from the design-time, and also want to discuss
the possiblity that make the workflow engine as mirco service and make the
designer more easy。
Best Regards
Maopeng
原始邮件
发件人： <[email protected]>
收件人：张茂鹏10030173
抄送人： <[email protected]> <[email protected]>
<[email protected]>
日 期 ：2017年07月20日 20:59
主 题 ：Re: 答复: Re: [onap-discuss] About workflow engine
I would like to focus our discussion on design-time change management workflows
(e.g., pause, upgrade etc.) and how current tooling fits into the overall SDC
architecture and UX.
Can I set a meeting for next Tuesday, 17:00 UTC+3?
Zahi Kapeluto
Lead Architect, Network Communications LOB
AT&T Network Applications Development · SD&E
Tel Aviv | Tampa | Atlanta | New Jersey | Chicago
·················································
Mobile: +972 (54) 6636831
Office: +972 (3) 9280064
From: "[email protected]" <[email protected]>
Date: Thursday, 20 July 2017 at 4:54
To: ZAHI KAPELUTO <[email protected]>
Cc: "[email protected]" <[email protected]>,
"[email protected]" <[email protected]>, "SACKS, ZOHAR"
<[email protected]>
Subject: 答复: Re: [onap-discuss] About workflow engine
Hi Zahi
Yes, definite. Workflow engines have different workflow templates. If
the workflow is designed by user via SDC, it will effect SDC.
In my mind, some workflow is used by user, maybe some workflow is used
only by the code developer as well, such as Camunda offline tools, DG offline
tools,....
However if the workflow design for user can be integrated with SDC via
portal SDK, It will be greater.
Best Regards
Maopeng
原始邮件
发件人： <[email protected]>
收件人：张茂鹏10030173 <[email protected]> <[email protected]>
抄送人： <[email protected]>
日 期 ：2017年07月20日 02:27
主 题 ：Re: [onap-discuss] About workflow engine
Can we also have a discussion about the workflow designer (which should be part
of SDC), its capabilities, proposed architecture etc.?
Zahi Kapeluto
Lead Architect, Network Communications LOB
AT&T Network Applications Development · SD&E
Tel Aviv | Tampa | Atlanta | New Jersey | Chicago
·················································
Mobile: +972 (54) 6636831
Office: +972 (3) 9280064
From: <[email protected]> on behalf of
"[email protected]" <[email protected]>
Date: Wednesday, 19 July 2017 at 12:46
To: "[email protected]" <[email protected]>,
"[email protected]" <[email protected]>
Subject: [onap-discuss] About workflow engine
Hi seshu and guys
About the workflow engine(WFE) usage, I have an idea and want to share in
the community, If I am wrong, please correct me.
In the SO or controllers projects of ONAP, there are many opensource party
workflow engines, such as Camunda, MSO, DG, aria tosca workflow engine, ...etc.
Most of those workflow engines now bind to the project.
Workflow engines self are independant fucntion and can be decoupled with the
specific project logic functions.
Could the projects make them as micro service? If some projects use the
same one, the WFE instance could be shared among them.
If possible, we can create an group or wiki page to discuss the issue.
Thanks all.
Best Regards
Maopeng_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
