Re: [Ganglia-developers] moving mod_multicpu out of ganglia to ganglia-modules-linux
Hi Daniel: I'd like to know whether the work you are doing can be migrated to GitHub: https://github.com/ganglia/gmond_c_modules I thought we all agreed to move our code repository to GitHub a little over a year ago. I'm not especially fond of having all these separate projects spread all over the place. Everything should be placed under one roof (GitHub) as much as possible. Thanks, Bernard On Mon, May 14, 2012 at 10:54 AM, Daniel Pocock dan...@pocock.com.au wrote: On 14/05/12 17:08, Carlo Marcelo Arenas Belon wrote: On Mon, May 14, 2012 at 01:17:19PM +0200, Daniel Pocock wrote: The mod_multicpu code in the main ganglia repo is Linux-only, while most of the other modules are cross-platform I think it might also work for cygwin but haven't really tried lately, if that is the case though it will remove this functionality from cygwin for no big gain IMHO. Just a few comments: - I think it may be good to have some (or maybe all?) modules as separate packages, especially if they are only for a single platform, as smaller packages are easier to release manage - the python modules seem to evolve faster than the C stuff, just as the web stuff has evolved quite a lot recently, Python code doesn't need any autotools integration either, so that stuff could also be a separate source tree, separate release cycles, etc - although I hammered together the gmond-linux package, 90% is other people's work, I believe I've done everything I can to credit people for that - but I'm also happy for other people to have commit access on that repository, Brad is also an admin there now and he can also grant access - given the correlation between Linux and Cygwin stuff, maybe ganglia-modules-linux can be renamed and can cover both platforms - or given the nature of git, it could be forked to create a ganglia-modules-cygwin? Most of the python modules are linux specific though, so would guess your comment was about native modules instead. The version in ganglia-modules-linux is based on the same code, with some small enhancements (using arrays instead of string comparisons) instead of having a forked version, why not make multi-cpu portable instead? and if you think your linux version is better, why not import it instead? I've also implemented the same for Solaris (see http://gmod-solaris.sourceforge.net) - there is little in common. In some ways I think the code is more readable if kept separate. I have no objection to contributing my mod_multicpu enhancements to the main project - the gmod-linux thing was started as a proof-of-concept for standalone module builds, I think it serves that purpose well and I only hope people use it as a starting point for similar activity. It should not be seen as something I made up because I don't want to contribute 100% to the main project: rather, it should be seen as a mark of respect for the modular architecture of the project. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
Re: [Ganglia-developers] moving mod_multicpu out of ganglia to ganglia-modules-linux
On 16/05/12 19:09, Bernard Li wrote: Hi Daniel: I'd like to know whether the work you are doing can be migrated to GitHub: https://github.com/ganglia/gmond_c_modules I thought we all agreed to move our code repository to GitHub a little over a year ago. I'm not especially fond of having all these separate projects spread all over the place. Everything should be placed under one roof (GitHub) as much as possible. I still keep roughly half the things I do on Sourceforge, not having all the eggs in one basket, as the saying goes But it is a git repo (not Sourceforge SVN), so a move to github would be trivial and I don't have any problem doing that. In particular, it makes sense having it under control of the `organisation' level access control that github offers now. I'll organise it later this week and send another email to confirm. Thanks, Bernard On Mon, May 14, 2012 at 10:54 AM, Daniel Pocock dan...@pocock.com.au wrote: On 14/05/12 17:08, Carlo Marcelo Arenas Belon wrote: On Mon, May 14, 2012 at 01:17:19PM +0200, Daniel Pocock wrote: The mod_multicpu code in the main ganglia repo is Linux-only, while most of the other modules are cross-platform I think it might also work for cygwin but haven't really tried lately, if that is the case though it will remove this functionality from cygwin for no big gain IMHO. Just a few comments: - I think it may be good to have some (or maybe all?) modules as separate packages, especially if they are only for a single platform, as smaller packages are easier to release manage - the python modules seem to evolve faster than the C stuff, just as the web stuff has evolved quite a lot recently, Python code doesn't need any autotools integration either, so that stuff could also be a separate source tree, separate release cycles, etc - although I hammered together the gmond-linux package, 90% is other people's work, I believe I've done everything I can to credit people for that - but I'm also happy for other people to have commit access on that repository, Brad is also an admin there now and he can also grant access - given the correlation between Linux and Cygwin stuff, maybe ganglia-modules-linux can be renamed and can cover both platforms - or given the nature of git, it could be forked to create a ganglia-modules-cygwin? Most of the python modules are linux specific though, so would guess your comment was about native modules instead. The version in ganglia-modules-linux is based on the same code, with some small enhancements (using arrays instead of string comparisons) instead of having a forked version, why not make multi-cpu portable instead? and if you think your linux version is better, why not import it instead? I've also implemented the same for Solaris (see http://gmod-solaris.sourceforge.net) - there is little in common. In some ways I think the code is more readable if kept separate. I have no objection to contributing my mod_multicpu enhancements to the main project - the gmod-linux thing was started as a proof-of-concept for standalone module builds, I think it serves that purpose well and I only hope people use it as a starting point for similar activity. It should not be seen as something I made up because I don't want to contribute 100% to the main project: rather, it should be seen as a mark of respect for the modular architecture of the project. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
Re: [Ganglia-developers] moving mod_multicpu out of ganglia to ganglia-modules-linux
Thanks Daniel! Cheers, Bernard On Wed, May 16, 2012 at 2:10 PM, Daniel Pocock dan...@pocock.com.au wrote: On 16/05/12 19:09, Bernard Li wrote: Hi Daniel: I'd like to know whether the work you are doing can be migrated to GitHub: https://github.com/ganglia/gmond_c_modules I thought we all agreed to move our code repository to GitHub a little over a year ago. I'm not especially fond of having all these separate projects spread all over the place. Everything should be placed under one roof (GitHub) as much as possible. I still keep roughly half the things I do on Sourceforge, not having all the eggs in one basket, as the saying goes But it is a git repo (not Sourceforge SVN), so a move to github would be trivial and I don't have any problem doing that. In particular, it makes sense having it under control of the `organisation' level access control that github offers now. I'll organise it later this week and send another email to confirm. Thanks, Bernard On Mon, May 14, 2012 at 10:54 AM, Daniel Pocock dan...@pocock.com.au wrote: On 14/05/12 17:08, Carlo Marcelo Arenas Belon wrote: On Mon, May 14, 2012 at 01:17:19PM +0200, Daniel Pocock wrote: The mod_multicpu code in the main ganglia repo is Linux-only, while most of the other modules are cross-platform I think it might also work for cygwin but haven't really tried lately, if that is the case though it will remove this functionality from cygwin for no big gain IMHO. Just a few comments: - I think it may be good to have some (or maybe all?) modules as separate packages, especially if they are only for a single platform, as smaller packages are easier to release manage - the python modules seem to evolve faster than the C stuff, just as the web stuff has evolved quite a lot recently, Python code doesn't need any autotools integration either, so that stuff could also be a separate source tree, separate release cycles, etc - although I hammered together the gmond-linux package, 90% is other people's work, I believe I've done everything I can to credit people for that - but I'm also happy for other people to have commit access on that repository, Brad is also an admin there now and he can also grant access - given the correlation between Linux and Cygwin stuff, maybe ganglia-modules-linux can be renamed and can cover both platforms - or given the nature of git, it could be forked to create a ganglia-modules-cygwin? Most of the python modules are linux specific though, so would guess your comment was about native modules instead. The version in ganglia-modules-linux is based on the same code, with some small enhancements (using arrays instead of string comparisons) instead of having a forked version, why not make multi-cpu portable instead? and if you think your linux version is better, why not import it instead? I've also implemented the same for Solaris (see http://gmod-solaris.sourceforge.net) - there is little in common. In some ways I think the code is more readable if kept separate. I have no objection to contributing my mod_multicpu enhancements to the main project - the gmod-linux thing was started as a proof-of-concept for standalone module builds, I think it serves that purpose well and I only hope people use it as a starting point for similar activity. It should not be seen as something I made up because I don't want to contribute 100% to the main project: rather, it should be seen as a mark of respect for the modular architecture of the project. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
[Ganglia-developers] moving mod_multicpu out of ganglia to ganglia-modules-linux
The mod_multicpu code in the main ganglia repo is Linux-only, while most of the other modules are cross-platform The version in ganglia-modules-linux is based on the same code, with some small enhancements (using arrays instead of string comparisons) Therefore, I'm simply going to leave it out of the core ganglia distribution - anyone who wants to use this module can still get it at http://gmod-linux.sourceforge.net/ -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
Re: [Ganglia-developers] moving mod_multicpu out of ganglia to ganglia-modules-linux
On Mon, May 14, 2012 at 01:17:19PM +0200, Daniel Pocock wrote: The mod_multicpu code in the main ganglia repo is Linux-only, while most of the other modules are cross-platform I think it might also work for cygwin but haven't really tried lately, if that is the case though it will remove this functionality from cygwin for no big gain IMHO. Most of the python modules are linux specific though, so would guess your comment was about native modules instead. The version in ganglia-modules-linux is based on the same code, with some small enhancements (using arrays instead of string comparisons) instead of having a forked version, why not make multi-cpu portable instead? and if you think your linux version is better, why not import it instead? having a mechanism to identify which OS is supported by each module was something that was missing in the modular architecture from the start (since it was modeled after apache that doesn't have that requirement) and adding this functionality instead of hacking around the lack of it would be IMHO a better option, eventhough that would most likely require a binary incompatible change and therefore a different (at least minor) version of ganglia, which seems is something we are fond of now anyway considering I'd seen some code released as 3.4 already. Carlo -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
