On 15.10.2013, at 14:45, Zane Bitter <zbit...@redhat.com> wrote:
> That said, can we please, please, please not invent a *third* meaning of
> "orchestration"? The proposal, as I understand it, is Workflow as a Service,
> so let's call it that. The fact that orchestration uses a workflow does not
> make them the same thing. OpenStack already has an Orchestration program,
> calling Mistral a "task scheduling and orchestration service" just adds
> confusion.
Yes, that's right. It's all up to discussion and I'm glad you mentioned that.
"Orchestration" seems now a very cool popular word in the community and lots of
discussions are now going on about it, mostly meaning Heat mission and design.
However, when we started this initiative we found word "orchestration" very
suitable for what we were planning with respect to task processing. I believe
we'll come to a non-confusing terminology while discussing all the details with
the community.
Thanks, very valuable note.
Renat
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
