Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-03-21 Thread Zane Bitter
Late to the party, but this comparison seems misleading to me... On 26/01/16 04:46, Steven Hardy wrote: It's one more thing, which is already maintained and has an active community, vs yet-another-bespoke-special-to-tripleo-thing. IMHO we have *way* too many tripleo specific things already. H

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-02-01 Thread Renat Akhmerov
> On 02 Feb 2016, at 03:55, Dan Prince wrote: > > On Mon, 2016-02-01 at 15:17 +0600, Renat Akhmerov wrote: >> Hi, >> >> I’ve read only part of letters in this huge interesting thread so far >> but I’d like to try to jump in and give some comments. >> >> API >> I personally don’t support using

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-02-01 Thread Dan Prince
On Mon, 2016-02-01 at 15:17 +0600, Renat Akhmerov wrote: > Hi, > > I’ve read only part of letters in this huge interesting thread so far > but I’d like to try to jump in and give some comments. > > API > I personally don’t support using Mistral API as is. Maybe you came to > agreement already abo

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-02-01 Thread Renat Akhmerov
Hi, I’ve read only part of letters in this huge interesting thread so far but I’d like to try to jump in and give some comments. API I personally don’t support using Mistral API as is. Maybe you came to agreement already about that, don’t know. I think that API should reflect user needs in spe

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-29 Thread Renat Akhmerov
> On 22 Jan 2016, at 20:01, Dan Prince wrote: > > https://github.com/dprince/tripleo-common/tree/mistral Just a couple of cosmetic notes: * this example can be slightly simplified by removing “type: direct” since by default workflows are of “direct” type. * action params don’t have to go on a

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-28 Thread Tzu-Mainn Chen
> On 27 January 2016 at 08:10, Tzu-Mainn Chen < tzuma...@redhat.com > wrote: > > > Okay, so I initially thought we weren't making much progress on this > > > > discussion, but after some more thought and reading of the existing PoC, > > > > we're (maybe?) less far apart than I initially thought.

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-28 Thread Steven Hardy
On Wed, Jan 27, 2016 at 10:22:54AM -0500, Dan Prince wrote: > On Wed, 2016-01-27 at 09:36 -0500, Dan Prince wrote: > > On Wed, 2016-01-27 at 14:32 +0100, Jiri Tomasek wrote: > > > On 01/26/2016 09:05 PM, Ben Nemec wrote: > > > > On 01/25/2016 04:36 PM, Dan Prince wrote: > > > > > On Mon, 2016-01-25

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-27 Thread Jiri Tomasek
On 01/27/2016 03:36 PM, Dan Prince wrote: On Wed, 2016-01-27 at 14:32 +0100, Jiri Tomasek wrote: On 01/26/2016 09:05 PM, Ben Nemec wrote: On 01/25/2016 04:36 PM, Dan Prince wrote: On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote: On 01/22/2016 06:19 PM, Dan Prince wrote: On Fri, 2016-01-22

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-27 Thread Dan Prince
On Wed, 2016-01-27 at 09:36 -0500, Dan Prince wrote: > On Wed, 2016-01-27 at 14:32 +0100, Jiri Tomasek wrote: > > On 01/26/2016 09:05 PM, Ben Nemec wrote: > > > On 01/25/2016 04:36 PM, Dan Prince wrote: > > > > On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote: > > > > > On 01/22/2016 06:19 PM, Da

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-27 Thread Tzu-Mainn Chen
> On Wed, 2016-01-27 at 09:36 -0500, Dan Prince wrote: > > On Wed, 2016-01-27 at 14:32 +0100, Jiri Tomasek wrote: > > > On 01/26/2016 09:05 PM, Ben Nemec wrote: > > > > On 01/25/2016 04:36 PM, Dan Prince wrote: > > > > > On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote: > > > > > > On 01/22/2016

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-27 Thread Dan Prince
On Wed, 2016-01-27 at 14:32 +0100, Jiri Tomasek wrote: > On 01/26/2016 09:05 PM, Ben Nemec wrote: > > On 01/25/2016 04:36 PM, Dan Prince wrote: > > > On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote: > > > > On 01/22/2016 06:19 PM, Dan Prince wrote: > > > > > On Fri, 2016-01-22 at 11:24 -0600, Be

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-27 Thread Dougal Matthews
On 26 January 2016 at 16:01, Ben Nemec wrote: > On 01/26/2016 03:46 AM, Steven Hardy wrote: > > On Mon, Jan 25, 2016 at 05:45:30PM -0600, Ben Nemec wrote: > >> On 01/25/2016 03:56 PM, Steven Hardy wrote: > >>> On Fri, Jan 22, 2016 at 11:24:20AM -0600, Ben Nemec wrote: > So I haven't weighed

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-27 Thread Dan Prince
On Tue, 2016-01-26 at 14:05 -0600, Ben Nemec wrote: > On 01/25/2016 04:36 PM, Dan Prince wrote: > > On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote: > > > On 01/22/2016 06:19 PM, Dan Prince wrote: > > > > On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: > > > > > So I haven't weighed in on th

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-27 Thread Dougal Matthews
On 27 January 2016 at 08:10, Tzu-Mainn Chen wrote: > > Okay, so I initially thought we weren't making much progress on this > > discussion, but after some more thought and reading of the existing PoC, > > we're (maybe?) less far apart than I initially thought. > > > > I think there are kind of th

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-27 Thread Jiri Tomasek
On 01/26/2016 09:05 PM, Ben Nemec wrote: On 01/25/2016 04:36 PM, Dan Prince wrote: On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote: On 01/22/2016 06:19 PM, Dan Prince wrote: On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: So I haven't weighed in on this yet, in part because I was on va

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-27 Thread Tzu-Mainn Chen
> Okay, so I initially thought we weren't making much progress on this > discussion, but after some more thought and reading of the existing PoC, > we're (maybe?) less far apart than I initially thought. > > I think there are kind of three different designs being discussed. > > 1) Rewrite a bunch

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-26 Thread Ben Nemec
On 01/25/2016 04:36 PM, Dan Prince wrote: > On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote: >> On 01/22/2016 06:19 PM, Dan Prince wrote: >>> On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: So I haven't weighed in on this yet, in part because I was on vacation when it was firs

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-26 Thread Steven Hardy
On Tue, Jan 26, 2016 at 10:01:56AM -0600, Ben Nemec wrote: > On 01/26/2016 03:46 AM, Steven Hardy wrote: > > On Mon, Jan 25, 2016 at 05:45:30PM -0600, Ben Nemec wrote: > >> On 01/25/2016 03:56 PM, Steven Hardy wrote: > >>> On Fri, Jan 22, 2016 at 11:24:20AM -0600, Ben Nemec wrote: > So I haven

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-26 Thread James Slagle
On Tue, Jan 26, 2016 at 10:46 AM, Dan Prince wrote: > On Mon, 2016-01-25 at 15:08 -0500, James Slagle wrote: > > > > > > On Mon, Jan 25, 2016 at 1:09 PM, Dan Prince > > wrote: > > > > > > As for tripleo-heat-templates... sure it hasn't been an entirely > > > smooth > > > ride. I think a lot of t

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-26 Thread Ben Nemec
On 01/26/2016 03:46 AM, Steven Hardy wrote: > On Mon, Jan 25, 2016 at 05:45:30PM -0600, Ben Nemec wrote: >> On 01/25/2016 03:56 PM, Steven Hardy wrote: >>> On Fri, Jan 22, 2016 at 11:24:20AM -0600, Ben Nemec wrote: So I haven't weighed in on this yet, in part because I was on vacation whe

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-26 Thread Dan Prince
On Tue, 2016-01-26 at 09:23 -0500, Tzu-Mainn Chen wrote: > - Original Message - > > On Mon, Jan 25, 2016 at 05:45:30PM -0600, Ben Nemec wrote: > > > On 01/25/2016 03:56 PM, Steven Hardy wrote: > > > > On Fri, Jan 22, 2016 at 11:24:20AM -0600, Ben Nemec wrote: > > > > > So I haven't weighed

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-26 Thread Dan Prince
On Mon, 2016-01-25 at 15:08 -0500, James Slagle wrote: > > > On Mon, Jan 25, 2016 at 1:09 PM, Dan Prince > wrote: > >   > > As for tripleo-heat-templates... sure it hasn't been an entirely > > smooth > > ride. I think a lot of the pain has to do with a lack of CI > > coverage on > > proper upgra

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-26 Thread James Slagle
On Tue, Jan 26, 2016 at 10:27 AM, Dan Prince wrote: > On Tue, 2016-01-26 at 09:56 -0500, James Slagle wrote: > > > > > > On Tue, Jan 26, 2016 at 9:08 AM, Steven Hardy > > wrote: > > > On Tue, Jan 26, 2016 at 07:40:05AM -0500, James Slagle wrote: > > > >On Tue, Jan 26, 2016 at 4:46 AM, Steven

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-26 Thread Tzu-Mainn Chen
- Original Message - > On Tue, Jan 26, 2016 at 09:23:00AM -0500, Tzu-Mainn Chen wrote: > > - Original Message - > > > On Mon, Jan 25, 2016 at 05:45:30PM -0600, Ben Nemec wrote: > > > > On 01/25/2016 03:56 PM, Steven Hardy wrote: > > > > > On Fri, Jan 22, 2016 at 11:24:20AM -0600, Be

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-26 Thread Dan Prince
On Tue, 2016-01-26 at 09:56 -0500, James Slagle wrote: > > > On Tue, Jan 26, 2016 at 9:08 AM, Steven Hardy > wrote: > > On Tue, Jan 26, 2016 at 07:40:05AM -0500, James Slagle wrote: > > >    On Tue, Jan 26, 2016 at 4:46 AM, Steven Hardy > om> wrote: > > > > > >      On Mon, Jan 25, 2016 at 05:4

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-26 Thread Steven Hardy
On Tue, Jan 26, 2016 at 09:23:00AM -0500, Tzu-Mainn Chen wrote: > - Original Message - > > On Mon, Jan 25, 2016 at 05:45:30PM -0600, Ben Nemec wrote: > > > On 01/25/2016 03:56 PM, Steven Hardy wrote: > > > > On Fri, Jan 22, 2016 at 11:24:20AM -0600, Ben Nemec wrote: > > > >> So I haven't we

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-26 Thread James Slagle
On Tue, Jan 26, 2016 at 9:08 AM, Steven Hardy wrote: > On Tue, Jan 26, 2016 at 07:40:05AM -0500, James Slagle wrote: > >On Tue, Jan 26, 2016 at 4:46 AM, Steven Hardy > wrote: > > > > On Mon, Jan 25, 2016 at 05:45:30PM -0600, Ben Nemec wrote: > > > On 01/25/2016 03:56 PM, Steven Har

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-26 Thread Tzu-Mainn Chen
- Original Message - > On Mon, Jan 25, 2016 at 05:45:30PM -0600, Ben Nemec wrote: > > On 01/25/2016 03:56 PM, Steven Hardy wrote: > > > On Fri, Jan 22, 2016 at 11:24:20AM -0600, Ben Nemec wrote: > > >> So I haven't weighed in on this yet, in part because I was on vacation > > >> when it was

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-26 Thread Steven Hardy
On Tue, Jan 26, 2016 at 07:40:05AM -0500, James Slagle wrote: >On Tue, Jan 26, 2016 at 4:46 AM, Steven Hardy wrote: > > On Mon, Jan 25, 2016 at 05:45:30PM -0600, Ben Nemec wrote: > > On 01/25/2016 03:56 PM, Steven Hardy wrote: > > > On Fri, Jan 22, 2016 at 11:24:20AM -0600, Ben

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-26 Thread James Slagle
On Tue, Jan 26, 2016 at 4:46 AM, Steven Hardy wrote: > On Mon, Jan 25, 2016 at 05:45:30PM -0600, Ben Nemec wrote: > > On 01/25/2016 03:56 PM, Steven Hardy wrote: > > > On Fri, Jan 22, 2016 at 11:24:20AM -0600, Ben Nemec wrote: > > >> So I haven't weighed in on this yet, in part because I was on v

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-26 Thread Jiri Tomasek
On 01/14/2016 12:54 PM, Steven Hardy wrote: On Wed, Jan 13, 2016 at 04:41:28AM -0500, Tzu-Mainn Chen wrote: Hey all, I realize now from the title of the other TripleO/Mistral thread [1] that the discussion there may have gotten confused. I think using Mistral for TripleO processes that are obv

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-26 Thread Steven Hardy
On Mon, Jan 25, 2016 at 05:45:30PM -0600, Ben Nemec wrote: > On 01/25/2016 03:56 PM, Steven Hardy wrote: > > On Fri, Jan 22, 2016 at 11:24:20AM -0600, Ben Nemec wrote: > >> So I haven't weighed in on this yet, in part because I was on vacation > >> when it was first proposed and missed a lot of the

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-25 Thread Hugh Brock
hI can't speak to any of the concerns below from an engineering standpoint, so I won't try. I do have the benefit of an earful from various tripleo users, and also of watching a lot of the history of tripleo development, so I will comment from that standpoint. On Tue, Jan 26, 2016 at 12:45 AM, Ben

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-25 Thread Ben Nemec
On 01/25/2016 03:56 PM, Steven Hardy wrote: > On Fri, Jan 22, 2016 at 11:24:20AM -0600, Ben Nemec wrote: >> So I haven't weighed in on this yet, in part because I was on vacation >> when it was first proposed and missed a lot of the initial discussion, >> and also because I wanted to take some time

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-25 Thread Dan Prince
On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote: > On 01/22/2016 06:19 PM, Dan Prince wrote: > > On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: > > > So I haven't weighed in on this yet, in part because I was on > > > vacation > > > when it was first proposed and missed a lot of the initial

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-25 Thread Steven Hardy
On Mon, Jan 25, 2016 at 03:08:07PM -0500, James Slagle wrote: >On Mon, Jan 25, 2016 at 1:09 PM, Dan Prince wrote: > > As for tripleo-heat-templates... sure it hasn't been an entirely smooth > ride. I think a lot of the pain has to do with a lack of CI coverage on > proper upgra

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-25 Thread Steven Hardy
On Fri, Jan 22, 2016 at 11:24:20AM -0600, Ben Nemec wrote: > So I haven't weighed in on this yet, in part because I was on vacation > when it was first proposed and missed a lot of the initial discussion, > and also because I wanted to take some time to order my thoughts on it. > Also because my i

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-25 Thread Ben Nemec
On 01/25/2016 05:56 AM, Dougal Matthews wrote: > Great post Ben, I largely agree with what you are saying, a lot of your > points > are valid concerns that I share. Just a couple of comments inline as I > try to > avoid what others have said. > > On 22 January 2016 at 17:24, Ben Nemec

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-25 Thread Ben Nemec
On 01/22/2016 06:19 PM, Dan Prince wrote: > On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: >> So I haven't weighed in on this yet, in part because I was on >> vacation >> when it was first proposed and missed a lot of the initial >> discussion, >> and also because I wanted to take some time to

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-25 Thread Dan Prince
On Mon, 2016-01-25 at 15:08 -0500, James Slagle wrote: > > > On Mon, Jan 25, 2016 at 1:09 PM, Dan Prince > wrote: > >   > > As for tripleo-heat-templates... sure it hasn't been an entirely > > smooth > > ride. I think a lot of the pain has to do with a lack of CI > > coverage on > > proper upgra

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-25 Thread James Slagle
On Mon, Jan 25, 2016 at 1:09 PM, Dan Prince wrote: > > As for tripleo-heat-templates... sure it hasn't been an entirely smooth > ride. I think a lot of the pain has to do with a lack of CI coverage on > proper upgrade paths upstream. I think this has less to do with the > architecture (certainly

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-25 Thread Dan Prince
On Mon, 2016-01-25 at 06:55 -0800, Clint Byrum wrote: > Excerpts from Jiri Tomasek's message of 2016-01-25 06:09:33 -0800: > > On 01/25/2016 12:42 AM, Clint Byrum wrote: > > > Excerpts from Dan Prince's message of 2016-01-22 16:19:07 -0800: > > > > On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-25 Thread Dan Prince
On Sun, 2016-01-24 at 15:42 -0800, Clint Byrum wrote: > Excerpts from Dan Prince's message of 2016-01-22 16:19:07 -0800: > > On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: > > > So I haven't weighed in on this yet, in part because I was on > > > vacation > > > when it was first proposed and mi

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-25 Thread Dan Prince
On Mon, 2016-01-25 at 09:32 -0500, James Slagle wrote: > > > On Mon, Jan 25, 2016 at 9:09 AM, Jiri Tomasek > wrote: > > On 01/25/2016 12:42 AM, Clint Byrum wrote: > > >  Excerpts from Dan Prince's message of 2016-01-22 16:19:07 -0800: > > > > > >   > > > >  I actually think rather than shieldin

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-25 Thread James Slagle
On Mon, Jan 25, 2016 at 6:56 AM, Dougal Matthews wrote: > Great post Ben, I largely agree with what you are saying, a lot of your > points > are valid concerns that I share. Just a couple of comments inline as I try > to > avoid what others have said. > > On 22 January 2016 at 17:24, Ben Nemec w

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-25 Thread Clint Byrum
Excerpts from Jiri Tomasek's message of 2016-01-25 06:09:33 -0800: > On 01/25/2016 12:42 AM, Clint Byrum wrote: > > Excerpts from Dan Prince's message of 2016-01-22 16:19:07 -0800: > >> On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: > >>> So I haven't weighed in on this yet, in part because I

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-25 Thread James Slagle
On Mon, Jan 25, 2016 at 9:09 AM, Jiri Tomasek wrote: > On 01/25/2016 12:42 AM, Clint Byrum wrote: > >> Excerpts from Dan Prince's message of 2016-01-22 16:19:07 -0800: >> > >> I actually think rather than shielding users we should be more >>> transparent about the actual workflows that are drivin

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-25 Thread Jiri Tomasek
On 01/25/2016 12:42 AM, Clint Byrum wrote: Excerpts from Dan Prince's message of 2016-01-22 16:19:07 -0800: On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: So I haven't weighed in on this yet, in part because I was on vacation when it was first proposed and missed a lot of the initial discu

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-25 Thread Dougal Matthews
Great post Ben, I largely agree with what you are saying, a lot of your points are valid concerns that I share. Just a couple of comments inline as I try to avoid what others have said. On 22 January 2016 at 17:24, Ben Nemec wrote: > So I haven't weighed in on this yet, in part because I was on

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-24 Thread Clint Byrum
Excerpts from Dan Prince's message of 2016-01-22 16:19:07 -0800: > On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: > > So I haven't weighed in on this yet, in part because I was on > > vacation > > when it was first proposed and missed a lot of the initial > > discussion, > > and also because I

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-24 Thread Adam Young
On 01/22/2016 09:01 AM, Dan Prince wrote: I gave a couple of ad-hoc demo's of my Mistral dev environment this week. For those interested in tinkering with TripleO Mistral actions in tripleo-common here are links to the code I used for those. Still a rough prototype but hopefully demonstrates how

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-22 Thread Dan Prince
On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: > So I haven't weighed in on this yet, in part because I was on > vacation > when it was first proposed and missed a lot of the initial > discussion, > and also because I wanted to take some time to order my thoughts on > it. >  Also because my in

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-22 Thread Jay Dobies
I fall very much in the same mentality as Ben. I'm +1 to all of his points, with a few comments inline. On 01/22/2016 12:24 PM, Ben Nemec wrote: So I haven't weighed in on this yet, in part because I was on vacation when it was first proposed and missed a lot of the initial discussion, and also

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-22 Thread Ben Nemec
On 01/22/2016 12:30 PM, Ryan Brady wrote: > > > On Fri, Jan 22, 2016 at 12:24 PM, Ben Nemec > wrote: > > So I haven't weighed in on this yet, in part because I was on vacation > when it was first proposed and missed a lot of the initial discussion, > a

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-22 Thread Ryan Brady
On Fri, Jan 22, 2016 at 12:24 PM, Ben Nemec wrote: > So I haven't weighed in on this yet, in part because I was on vacation > when it was first proposed and missed a lot of the initial discussion, > and also because I wanted to take some time to order my thoughts on it. > Also because my initial

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-22 Thread Ben Nemec
So I haven't weighed in on this yet, in part because I was on vacation when it was first proposed and missed a lot of the initial discussion, and also because I wanted to take some time to order my thoughts on it. Also because my initial reaction...was not conducive to calm and rational discussion

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-22 Thread Dan Prince
I gave a couple of ad-hoc demo's of my Mistral dev environment this week. For those interested in tinkering with TripleO Mistral actions in tripleo-common here are links to the code I used for those. Still a rough prototype but hopefully demonstrates how these things might work: https://github.com

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-21 Thread Ryan Brady
On Thu, Jan 21, 2016 at 10:29 AM, Tzu-Mainn Chen wrote: > > > > > On 21 January 2016 at 14:46, Dougal Matthews wrote: >> >> >> >> On 20 January 2016 at 20:05, Tzu-Mainn Chen wrote: >>> >>> - Original Message - >>> > On 18.1.2016 19:49, Tzu-Mainn Chen wrot

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-21 Thread Tzu-Mainn Chen
- Original Message - > On 21 January 2016 at 14:46, Dougal Matthews < dou...@redhat.com > wrote: > > On 20 January 2016 at 20:05, Tzu-Mainn Chen < tzuma...@redhat.com > wrote: > > > > - Original Message - > > > > > > > On 18.1.2016 19:49, Tzu-Mainn Chen wrote: > > > > > > >

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-21 Thread Dougal Matthews
On 21 January 2016 at 14:46, Dougal Matthews wrote: > > > On 20 January 2016 at 20:05, Tzu-Mainn Chen wrote: > >> - Original Message - >> > On 18.1.2016 19:49, Tzu-Mainn Chen wrote: >> > > - Original Message - >> > >> On Thu, 2016-01-14 at 16:04 -0500, Tzu-Mainn Chen wrote: >> >

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-21 Thread Dougal Matthews
On 20 January 2016 at 20:05, Tzu-Mainn Chen wrote: > - Original Message - > > On 18.1.2016 19:49, Tzu-Mainn Chen wrote: > > > - Original Message - > > >> On Thu, 2016-01-14 at 16:04 -0500, Tzu-Mainn Chen wrote: > > >>> > > >>> - Original Message - > > On Wed, Jan 13,

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-20 Thread Tzu-Mainn Chen
- Original Message - > On 18.1.2016 19:49, Tzu-Mainn Chen wrote: > > - Original Message - > >> On Thu, 2016-01-14 at 16:04 -0500, Tzu-Mainn Chen wrote: > >>> > >>> - Original Message - > On Wed, Jan 13, 2016 at 04:41:28AM -0500, Tzu-Mainn Chen wrote: > > Hey all, >

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-20 Thread Dougal Matthews
On 20 January 2016 at 10:03, Jiří Stránský wrote: > On 18.1.2016 19:49, Tzu-Mainn Chen wrote: > >> - Original Message - >> >>> On Thu, 2016-01-14 at 16:04 -0500, Tzu-Mainn Chen wrote: >>> - Original Message - > On Wed, Jan 13, 2016 at 04:41:28AM -0500, Tzu-Mainn

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-20 Thread Jiří Stránský
On 18.1.2016 19:49, Tzu-Mainn Chen wrote: - Original Message - On Thu, 2016-01-14 at 16:04 -0500, Tzu-Mainn Chen wrote: - Original Message - On Wed, Jan 13, 2016 at 04:41:28AM -0500, Tzu-Mainn Chen wrote: Hey all, I realize now from the title of the other TripleO/Mistral thr

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-18 Thread Tzu-Mainn Chen
- Original Message - > On Thu, 2016-01-14 at 16:04 -0500, Tzu-Mainn Chen wrote: > > > > - Original Message - > > > On Wed, Jan 13, 2016 at 04:41:28AM -0500, Tzu-Mainn Chen wrote: > > > > Hey all, > > > > > > > > I realize now from the title of the other TripleO/Mistral thread > >

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-15 Thread Dan Prince
On Thu, 2016-01-14 at 16:04 -0500, Tzu-Mainn Chen wrote: > > - Original Message - > > On Wed, Jan 13, 2016 at 04:41:28AM -0500, Tzu-Mainn Chen wrote: > > > Hey all, > > > > > > I realize now from the title of the other TripleO/Mistral thread > > > [1] that > > > the discussion there may h

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-14 Thread Tzu-Mainn Chen
- Original Message - > On Wed, Jan 13, 2016 at 04:41:28AM -0500, Tzu-Mainn Chen wrote: > > Hey all, > > > > I realize now from the title of the other TripleO/Mistral thread [1] that > > the discussion there may have gotten confused. I think using Mistral for > > TripleO processes that a

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-14 Thread Steven Hardy
On Wed, Jan 13, 2016 at 04:41:28AM -0500, Tzu-Mainn Chen wrote: > Hey all, > > I realize now from the title of the other TripleO/Mistral thread [1] that > the discussion there may have gotten confused. I think using Mistral for > TripleO processes that are obviously workflows - stack deployment,

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-13 Thread Tzu-Mainn Chen
- Original Message - > On Wed, 2016-01-13 at 04:41 -0500, Tzu-Mainn Chen wrote: > > Hey all, > > > > I realize now from the title of the other TripleO/Mistral thread [1] > > that > > the discussion there may have gotten confused.  I think using Mistral > > for > > TripleO processes that ar

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-13 Thread Dan Prince
On Wed, 2016-01-13 at 04:41 -0500, Tzu-Mainn Chen wrote: > Hey all, > > I realize now from the title of the other TripleO/Mistral thread [1] > that > the discussion there may have gotten confused.  I think using Mistral > for > TripleO processes that are obviously workflows - stack deployment, > n

[openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

2016-01-13 Thread Tzu-Mainn Chen
Hey all, I realize now from the title of the other TripleO/Mistral thread [1] that the discussion there may have gotten confused. I think using Mistral for TripleO processes that are obviously workflows - stack deployment, node registration - makes perfect sense. That thread is exploring practic