I am working around the issue of shared data available from the install hook
by using facter and my own facter-plugins. I still think it is a good idea
for ensemble to provide a mechanism by which the information can be
stored/shared/accessed from the install hook and not necessarily wait for
the relationships to start.
-Juan
On Tue, Jul 5, 2011 at 7:14 PM, Gustavo Niemeyer <email address hidden>wrote:
> I don't think I understand the problem. Hooks reflect specific events,
> and do not enforce in any way what you're supposed to be doing within
> them. The install hook, by design, is called just once when the formula
> is first installed, and in general is a convenient location to run
> installation of software. That said, there's nothing preventing you
> from running logic in any of the other hooks. If you can only
> install/start the software when a relation is established, you should
> feel free to do so.
>
>
> ** Changed in: ensemble
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/806098
>
> Title:
> fact repository for Ensemble
>
> Status in Ensemble:
> Incomplete
>
> Bug description:
> In Ensemble, once a relationship is made, the hooks are called that
> allow the creation of relationship bits via relation-set <blah>=<value
> of blah>.
>
> During the install script, there is no apparent mechanism by which to
> start saving variables and their corresponding values. Maybe this is
> a design issue but, there are formulas the need to have information
> preserved at the install level and not at the relationship level.
>
> A good example of this is tomcat: In tomcat, the server.xml file
> needs to be created with static members that require a unique
> identifier as well as a unique id for each node of the "cluster".
>
> The problem with this is that when the peer-relation hook is called it
> will only have the necessary information of the remote host but not
> that of itself.
>
> I can ( on install ) write all of the necessary values to a file and
> work from there but, I believe an equivalent command to relation-
> set/get/list that can be used during the install hook-script would be
> very useful. Of course the information needs to also be available
> during the relation-get/set/list commands.
>
> This information ( or fact-db ) will become increasingly necessary as
> we continue to develop and deploy formulas that require uuid's and
> clusternames for their proper clustering ( ie: cassandra,
> cloudfoundry, tomcat, mondgodb, etc.)
>
> -Juan
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ensemble/+bug/806098/+subscriptions
>
I am working around the issue of shared data available from the install hook shared/ accessed from the install hook and not necessarily wait for
by using facter and my own facter-plugins. I still think it is a good idea
for ensemble to provide a mechanism by which the information can be
stored/
the relationships to start.
-Juan
On Tue, Jul 5, 2011 at 7:14 PM, Gustavo Niemeyer <email address hidden>wrote:
> I don't think I understand the problem. Hooks reflect specific events, /bugs.launchpad .net/bugs/ 806098 get/set/ list commands. /bugs.launchpad .net/ensemble/ +bug/806098/ +subscriptions
> and do not enforce in any way what you're supposed to be doing within
> them. The install hook, by design, is called just once when the formula
> is first installed, and in general is a convenient location to run
> installation of software. That said, there's nothing preventing you
> from running logic in any of the other hooks. If you can only
> install/start the software when a relation is established, you should
> feel free to do so.
>
>
> ** Changed in: ensemble
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> fact repository for Ensemble
>
> Status in Ensemble:
> Incomplete
>
> Bug description:
> In Ensemble, once a relationship is made, the hooks are called that
> allow the creation of relationship bits via relation-set <blah>=<value
> of blah>.
>
> During the install script, there is no apparent mechanism by which to
> start saving variables and their corresponding values. Maybe this is
> a design issue but, there are formulas the need to have information
> preserved at the install level and not at the relationship level.
>
> A good example of this is tomcat: In tomcat, the server.xml file
> needs to be created with static members that require a unique
> identifier as well as a unique id for each node of the "cluster".
>
> The problem with this is that when the peer-relation hook is called it
> will only have the necessary information of the remote host but not
> that of itself.
>
> I can ( on install ) write all of the necessary values to a file and
> work from there but, I believe an equivalent command to relation-
> set/get/list that can be used during the install hook-script would be
> very useful. Of course the information needs to also be available
> during the relation-
>
> This information ( or fact-db ) will become increasingly necessary as
> we continue to develop and deploy formulas that require uuid's and
> clusternames for their proper clustering ( ie: cassandra,
> cloudfoundry, tomcat, mondgodb, etc.)
>
> -Juan
>
> To manage notifications about this bug go to:
> https:/
>