Comment 5 for bug 806098

relationships are not related to facts. I just see the need for facts so I
can save/precompute information at the install hook that can then be shared
with the other hooks ( or be available at the
relation-name-relationship-create/change level ).

ie: tomcat static members for it's cluster configuration require a
clustername that should be shared at install ( when the configuration takes
place ). Having this information handy could be useful when add-node is
used and the peer relationship hook gets called. The information created at
the install hook would now be available at the relationship-create hook.

Once I have the formula finished, I'll push it to the branch and you can
have a look at what I'm doing with it. Maybe that will clarify some things.

-Juan

On Tue, Jul 5, 2011 at 8:34 PM, Gustavo Niemeyer <email address hidden>wrote:

> It's still not entirely clear what you're looking for. You're using
> facters for what, more precisely, and how's that connected with
> relationships?
>
> relation-set is specific to the relation being changed, so it's impossible
> to have it during the install hook,
> because there are no relations established at this point.
>
> --
> 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
>