Re: [openstack-dev] [TripleO] Deployment workflow changes for ui/client

2017-10-24 Thread Emilien Macchi
On Tue, Oct 24, 2017 at 8:16 AM, James Slagle wrote: > On Tue, Oct 24, 2017 at 6:04 AM, Jiri Tomasek wrote: >> Having a workflow which wraps whole deployment sounds great from the UI side >> too as it allows us to simplify the steps you described

Re: [openstack-dev] [TripleO] Deployment workflow changes for ui/client

2017-10-24 Thread James Slagle
On Tue, Oct 24, 2017 at 6:04 AM, Jiri Tomasek wrote: > Having a workflow which wraps whole deployment sounds great from the UI side > too as it allows us to simplify the steps you described above. IIRC the > reason the whole deployment did not get wrapped into a single

Re: [openstack-dev] [TripleO] Deployment workflow changes for ui/client

2017-10-24 Thread Jiri Tomasek
On Fri, Oct 20, 2017 at 1:20 PM, Brad P. Crochet wrote: > On Thu, Oct 19, 2017 at 4:56 PM James Slagle > wrote: > >> I've been looking at how we can hook up the deployment changes for >> config-download[1] with the existing deployment workflows in

Re: [openstack-dev] [TripleO] Deployment workflow changes for ui/client

2017-10-20 Thread Brad P. Crochet
On Thu, Oct 19, 2017 at 4:56 PM James Slagle wrote: > I've been looking at how we can hook up the deployment changes for > config-download[1] with the existing deployment workflows in Mistral. > > However, it seems we have not sufficiently abstracted the logic to do > a

[openstack-dev] [TripleO] Deployment workflow changes for ui/client

2017-10-19 Thread James Slagle
I've been looking at how we can hook up the deployment changes for config-download[1] with the existing deployment workflows in Mistral. However, it seems we have not sufficiently abstracted the logic to do a "deployment" behind a given workflow(s). The existing things a client (or UI) has to do