[PATCH conductor] #3391 Represent the relationships between instances

Jozef Zigmund jzigmund at redhat.com
Mon Jul 16 16:04:55 UTC 2012


> Hi Jozef,
> I didn't have time to do a proper review yet, but have a few findings 
> about this so far:
> - graphviz has many pkg dependencies (it added 41 new pkgs). Maybe it 
> could be optional - if graphviz is not installed, one some warning about 
> missing graphviz would be displayed.

Yes this can be added if we decide to use graphviz for displaying the
dependencies.

> - there is also already packaged graphviz-ruby gem - couldn't this be 
> used? I didn't check this, maybe it's not sufficient, but it could save 
> us some packaging

It's packaged bindings (Ruby extension) to graphviz, not the rubygem
(http://rubygems.org/gems/ruby-graphviz)

In fact we could use the same way as DC is using graphviz. It displays
graphs (instance states) throught DOT file. Then we dont need to package
anything, just add RPM dependency to graphviz and graphviz-ruby
packages.

> - it seems that this code generates dependencies between assemblies, 
> what we need are dependencies between services: so nodes would be 
> services, edges would represent param references, assembly would be 
> represented by a frame around services belonging to this assembly.

The output picture was not described so I've made it as proof of
concept.

> I checked deployable xml schema and what confuses me is that it seems 
> that a service param can reference a service _or_ an assembly (according 
> to param definition in app/util/deployable-rng.xml).
There is:

<element name="reference">
  <attribute name="assembly"><text/></attribute>
  <choice>
    <attribute name="parameter"><text/></attribute>
    <attribute name="service"><text/></attribute>
  </choice>
</element>

>  If a param 
> references assembly, then we can't resolve dependencies between 
> services.
If you check
https://www.aeolusproject.org/redmine/projects/aeolus/wiki/Deployable_XML
If I get it right, it can refer to other assembly return parameter(s)
what is basically referencing to other assembly's service.

>  Dan, you are most familiar with this - what do you think about 
> it? As I understand it, referencing whole assemblies should be disabled.
> 
> Jan

-- 
Jozef Zigmund




More information about the aeolus-devel mailing list