[
https://issues.apache.org/jira/browse/BIGTOP-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14222096#comment-14222096
]
jay vyas edited comment on BIGTOP-1507 at 11/22/14 5:55 PM:
------------------------------------------------------------
FYI, a *tangential* note, regarding *puppet recipes*... we also discussed
visualization. You can build jpg graphviz diagrams on the fly like this !
{{sudo puppet apply -d --confdir=/bigtop-home/bigtop-deploy/puppet/
--modulepath=/bigtop-home/bigtop-deploy/puppet/modules
/bigtop-home/bigtop-deploy/puppet/manifests/site.pp --noop --graph}}
And then
{{dot -Tjpg /var/lib/puppet/state/graphs/relationships.dot}}
To generate **graphviz** files for the puppet stuff. possibly we can upload
those to the website as part of the site publishing process. (see attached file)
was (Author: jayunit100):
FYI, a *tangential* note, regarding *puppet recipes*... we also discussed
visualization. You can build jpg graphviz diagrams on the fly like this !
{{sudo puppet apply -d --confdir=/bigtop-home/bigtop-deploy/puppet/
--modulepath=/bigtop-home/bigtop-deploy/puppet/modules
/bigtop-home/bigtop-deploy/puppet/manifests/site.pp --noop --graph}}
And then
{{dot -Tjpg /var/lib/puppet/state/graphs/relationships.dot}}
To generate **graphviz** files for the puppet stuff. possibly we can upload
those to the website as part of the site publishing process.
> Maintain explicit CI and Bigtop Architecture info in Bigtop
> -----------------------------------------------------------
>
> Key: BIGTOP-1507
> URL: https://issues.apache.org/jira/browse/BIGTOP-1507
> Project: Bigtop
> Issue Type: Task
> Components: documentation
> Affects Versions: 0.8.0
> Reporter: jay vyas
> Fix For: 0.9.0
>
> Attachments: bigtop.jpg
>
>
> Since CI Artifacts and Testing are quite sophisticated for bigtop, lets
> curate as part of the source a graphviz file which diagrams the bigtop
> architecture and outputs.
> That way - our infra is transparent and we can all pitch in to lend a hand .
> Better yet, maybe we can all play around with different CI's (that is really
> the value of docker i think - it makes the build server a much less fragile
> and easily replaced element of the stack).
> And an image is worth 1000 words, so i think rather than another README, a
> good graphviz file to generate the diagram of CI will be awesome.
> Also, we can in the diagram contain how to use the vagrant docker recipes to
> test build artifacts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
