On 24-Sep-14 00:25, Joshua Harlow wrote:
I believe heat has its own dependency graph implementation but if that was
switched to networkx[1] that library has a bunch of nice read/write
capabilities.
See: https://github.com/networkx/networkx/tree/master/networkx/readwrite
And one made for
On 23-Sep-14 09:42, Clint Byrum wrote:
Excerpts from Angus Salkeld's message of 2014-09-22 20:15:43 -0700:
On Tue, Sep 23, 2014 at 1:09 AM, Anant Patil anant.pa...@hp.com wrote:
Hi,
One of the steps in the direction of convergence is to enable Heat
engine to handle concurrent stack
On 23/09/14 09:44, Anant Patil wrote:
On 23-Sep-14 09:42, Clint Byrum wrote:
Excerpts from Angus Salkeld's message of 2014-09-22 20:15:43 -0700:
On Tue, Sep 23, 2014 at 1:09 AM, Anant Patil anant.pa...@hp.com wrote:
Hi,
One of the steps in the direction of convergence is to enable Heat
I believe heat has its own dependency graph implementation but if that was
switched to networkx[1] that library has a bunch of nice read/write
capabilities.
See: https://github.com/networkx/networkx/tree/master/networkx/readwrite
And one made for sqlalchemy @
Hi,
One of the steps in the direction of convergence is to enable Heat
engine to handle concurrent stack operations. The main convergence spec
talks about it. Resource versioning would be needed to handle concurrent
stack operations.
As of now, while updating a stack, a backup stack is created
On Tue, Sep 23, 2014 at 1:09 AM, Anant Patil anant.pa...@hp.com wrote:
Hi,
One of the steps in the direction of convergence is to enable Heat
engine to handle concurrent stack operations. The main convergence spec
talks about it. Resource versioning would be needed to handle concurrent
Excerpts from Angus Salkeld's message of 2014-09-22 20:15:43 -0700:
On Tue, Sep 23, 2014 at 1:09 AM, Anant Patil anant.pa...@hp.com wrote:
Hi,
One of the steps in the direction of convergence is to enable Heat
engine to handle concurrent stack operations. The main convergence spec
