>>> On 1/9/2008 at 9:29 PM, in message <[EMAIL PROTECTED]>, Matthias Blankenhaus <[EMAIL PROTECTED]> wrote: > Howdy ! > > I have noticed that some Python modules live under gmond/python_modules/. > On the other hand I remember that during our last meeting in SF 2007 we > had talked about a module repository a la http://www.ganglia.info/gmetric/. > > I wanted to start writing a Python module providing ipmi support to pull > HW metrics from BMCs and I wonder where it should reside ? > > One idea could be to put _basic_ or _general_ modules in the trunk and > more specific modules in a repository similar to the gmetric one. We > could even upload the Python DSO's as of today to the gmetric page. > However, my specific module would require a good amount of documentation > and I would rather not put this all in the source code. > > However, I am concerned that the module web location might not be that > well-known and thus people will miss it. Thus, the idea would be > to implement the Python DSO's as eggs and provide > the Ganglia distro with the necessary Python easy install configuration to > allow for over the net egg installation from the Ganglia egg manager. > But maybe I am paranoid here. > > What do people think about this ? >
I think that this is a very good discussion that we need to start. I believe that Bernard has already restructured the RPMs to build the python support and modules into a separate RPM outside of the core. This is a good first step but I think that we need to move more towards the ideas that you bring up here and that we discussed in SF. I like the idea of creating a python egg repository that would allow "blessed" modules to be easily downloaded and installed on a system. I also like the idea of a general 'gmetric' type of repository where users could contribute and share modules. In addition to that, I think that there should be a migration path from the 'general' repository to the 'blessed' repository. In other words, as modules are contributed to the 'general' repository, the more popular, useful, generic, multi-platform compatible (whatever criteria we want to use here) module source code would be migrated into the SVN repository. This would allow the module code to continue to be developed and/or maintained under source code control. The module would also be incorporated into the Ganglia build system which would automatically build the module into an egg. The egg would then be placed into the Ganglia installable module repository so that it can be easily installed and configured on a users system. Having a 'general' and a 'blessed' repository would allow anybody to contribute and share modules as well as allow the Ganglia project to glean the more useful and mutli-platform modules into a repository that allows them to be more easily maintained and deployed. Of course there would have to be some policy and procedure around the migration process such as source code licensing and source code developer support, but I think that all of that could be worked out. As for now, you should probably just put your new module source code under the gmond/python_modules directory. As we move forward, we can decide where to move all of the current python modules. Brad ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Ganglia-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-developers
