Hi,
Seems like most of the questions raised in the thread have been answered. Just
some clarifications on Mistral+Zaqar from my side:
Mistral integration with Zaqar still doesn’t exist although has been very much
wanted for a while. In its most trivial form it’s just a matter of adding Zaqar
On 01/11/2016 11:09 PM, Tzu-Mainn Chen wrote:
- Original Message -
Background info:
We've got a problem in TripleO at the moment where many of our
workflows can be driven by the command line only. This causes some
problems for those trying to build a UI around the workflows in that
On Tue, 2016-01-12 at 12:52 +0100, Jiri Tomasek wrote:
> On 01/11/2016 04:51 PM, Dan Prince wrote:
> > Background info:
> >
> > We've got a problem in TripleO at the moment where many of our
> > workflows can be driven by the command line only. This causes some
> > problems for those trying to
On 01/11/2016 04:51 PM, Dan Prince wrote:
Background info:
We've got a problem in TripleO at the moment where many of our
workflows can be driven by the command line only. This causes some
problems for those trying to build a UI around the workflows in that
they have to duplicate deployment
> On 01/11/2016 11:09 PM, Tzu-Mainn Chen wrote:
> > - Original Message -
> >> Background info:
> >>
> >> We've got a problem in TripleO at the moment where many of our
> >> workflows can be driven by the command line only. This causes some
> >> problems for those trying to build a UI
On 01/12/2016 08:24 AM, Dan Prince wrote:
On Tue, 2016-01-12 at 12:52 +0100, Jiri Tomasek wrote:
On 01/11/2016 04:51 PM, Dan Prince wrote:
Background info:
[snip]
In similar manner, is Mistral able to provide a way to get workflow
in
progress data? E.g. We have a Mistral workflow for nodes
On 01/12/2016 06:52 AM, Jiri Tomasek wrote:
On 01/11/2016 04:51 PM, Dan Prince wrote:
Background info:
We've got a problem in TripleO at the moment where many of our
workflows can be driven by the command line only. This causes some
problems for those trying to build a UI around the workflows
On 01/12/2016 04:22 PM, Ryan Brown wrote:
On 01/12/2016 06:52 AM, Jiri Tomasek wrote:
On 01/11/2016 04:51 PM, Dan Prince wrote:
Background info:
We've got a problem in TripleO at the moment where many of our
workflows can be driven by the command line only. This causes some
problems for those
On 01/12/2016 10:50 AM, Jiri Tomasek wrote:
On 01/12/2016 04:22 PM, Ryan Brown wrote:
On 01/12/2016 06:52 AM, Jiri Tomasek wrote:
On 01/11/2016 04:51 PM, Dan Prince wrote:
Background info:
We've got a problem in TripleO at the moment where many of our
workflows can be driven by the command
On Tue, 2016-01-12 at 13:24 -0500, Ryan Brown wrote:
> On 01/12/2016 10:50 AM, Jiri Tomasek wrote:
> > On 01/12/2016 04:22 PM, Ryan Brown wrote:
> > > On 01/12/2016 06:52 AM, Jiri Tomasek wrote:
> > > > On 01/11/2016 04:51 PM, Dan Prince wrote:
> > > > > Background info:
> > > > >
> > > > > We've
- Original Message -
> Background info:
>
> We've got a problem in TripleO at the moment where many of our
> workflows can be driven by the command line only. This causes some
> problems for those trying to build a UI around the workflows in that
> they have to duplicate deployment logic
Background info:
We've got a problem in TripleO at the moment where many of our
workflows can be driven by the command line only. This causes some
problems for those trying to build a UI around the workflows in that
they have to duplicate deployment logic in potentially multiple places.
There are
12 matches
Mail list logo
