: [openstack-dev] [UX] [Heat] [Mistral] Merlin project PoC update:
shift from HOT builder to Mistral Workbook builder
On Fri, Sep 26, 2014 at 7:04 AM, Steve Baker
sba...@redhat.commailto:sba...@redhat.com wrote:
On 26/09/14 05:36, Timur Sufiev wrote:
Hello, folks!
Following Drago Rosson's
Ok, Timur, thanks. Will check it out by the end of this week.
Renat Akhmerov
@ Mirantis Inc.
On 06 Oct 2014, at 20:16, Timur Sufiev tsuf...@mirantis.com wrote:
Renat,
I've addressed a number of Mistral Workbook builder's issues, including:
* separating workflow-based Tasks from
Renat,
I've addressed a number of Mistral Workbook builder's issues, including:
* separating workflow-based Tasks from action-based ones, including
distinct set of fields for each one;
* restricting the range of values that can be selected for 'required' field
of Task inside reverse-type
Timur,
For us, undoubtedly, it’s a great news. Visualization of any kind is really
important for Mistral for a number of reasons. You can count on any
help(including code contribution) from our side.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 26 Sep 2014, at 04:04, Steve Baker
On Fri, Sep 26, 2014 at 7:04 AM, Steve Baker sba...@redhat.com wrote:
On 26/09/14 05:36, Timur Sufiev wrote:
Hello, folks!
Following Drago Rosson's introduction of Barricade.js and our discussion
in ML about possibility of using it in Merlin [1], I've decided to change
the plans for PoC:
On 26/09/14 05:36, Timur Sufiev wrote:
Hello, folks!
Following Drago Rosson's introduction of Barricade.js and our
discussion in ML about possibility of using it in Merlin [1], I've
decided to change the plans for PoC: now the goal for Merlin's PoC is
to implement Mistral Workbook builder on