Hi Steven,
Steven Hardy sha...@redhat.com wrote on 10/21/2013 11:27:43 AM:
On Fri, Oct 18, 2013 at 02:45:01PM -0400, Lakshminaraya Renganarayana
wrote:
snip
The prototype is implemented in Python and Ruby is used for chef
interception.
Where can we find the code?
What part of the code
Hi Lakshmi,
you mentioned an example in your original post, but I did not find it. Can
you add the example?
Lakshminaraya Renganarayana lren...@us.ibm.com wrote on 18.10.2013
20:57:43:
From: Lakshminaraya Renganarayana lren...@us.ibm.com
To: OpenStack Development Mailing List
Hi Lakshminarayanan,
Seems like a solid plan.
I'm probably wrong here but ain't this too tied to chef? I believe the
solution should equally be suitable for chef, puppet, SaltStack, Murano, or
maybe all I need is just a plain bash script execution. It may be difficult
to intercept script reads
Hi Stan,
Thanks for the comments. As you have observed the prototype that I have
built is tied to Chef. I just wanted to describe that here for reference
and not as a proposal for the general implementation. What I would like to
work on is a more general solution that is agnostic to (or works
Thomas Spatzier thomas.spatz...@de.ibm.com wrote on 10/21/2013 08:29:47
AM:
you mentioned an example in your original post, but I did not find it.
Can
you add the example?
Hi Thomas,
Here is the example I used earlier:
For example, consider
a two VM app, with VMs vmA, vmB, and a set of
On Fri, Oct 18, 2013 at 02:45:01PM -0400, Lakshminaraya Renganarayana wrote:
snip
The prototype is implemented in Python and Ruby is used for chef
interception.
Where can we find the code?
___
OpenStack-dev mailing list
Hi,
In the last Openstack Heat meeting there was good interest in proposals for
cross-vm synchronization and communication and I had mentioned the
prototype I have built. I had also promised that I will post an outline of
the prototype ... Here it is. I might have missed some details, please
Just wanted to add a couple of clarifications:
1. the cross-vm dependences are captured via the read/writes of attributes
in resources and in software components (described in metadata sections).
2. these dependences are then realized via blocking-reads and writes to
zookeeper, which realizes
