- Original Message -
> On 12/07/2015 04:33 AM, Tzu-Mainn Chen wrote:
> >
> >
> > On 04/12/15 23:04, Dmitry Tantsur wrote:
> >
> > On 12/03/2015 08:45 PM, Tzu-Mainn Chen wrote:
> >
>
> >
> >
> >
On 12/07/2015 04:33 AM, Tzu-Mainn Chen wrote:
On 04/12/15 23:04, Dmitry Tantsur wrote:
On 12/03/2015 08:45 PM, Tzu-Mainn Chen wrote:
5. In-Progress Development
The initial spec
- Original Message -
> On 04/12/15 23:04, Dmitry Tantsur wrote:
> > On 12/03/2015 08:45 PM, Tzu-Mainn Chen wrote:
>
> > > Hey all,
> >
>
> > > Over the past few months, there's been a lot of discussion and work
> > > around
> >
>
> > > creating a new REST API-supported TripleO
On 04/12/15 23:04, Dmitry Tantsur wrote:
On 12/03/2015 08:45 PM, Tzu-Mainn Chen wrote:
Hey all,
Over the past few months, there's been a lot of discussion and work
around
creating a new REST API-supported TripleO deployment workflow.
However most
of that discussion has been fragmented within
On 12/03/2015 08:45 PM, Tzu-Mainn Chen wrote:
Hey all,
Over the past few months, there's been a lot of discussion and work around
creating a new REST API-supported TripleO deployment workflow. However most
of that discussion has been fragmented within spec reviews and weekly IRC
meetings, so I
Hey all,
Over the past few months, there's been a lot of discussion and work around
creating a new REST API-supported TripleO deployment workflow. However most
of that discussion has been fragmented within spec reviews and weekly IRC
meetings, so I thought it might make sense to provide a
