When we provision our cluster nodes, we have a static base image (eg. OS 
files, networking config, etc.), that is shared by all cluster nodes. We 
then "overlay" custom software stacks (eg. /opt or /usr/local) on top of 
the base image.

For us /usr/lib64 is part of the base image and we would prefer to have 
custom stuff, such as our in-house gmond modules, not installed into the 
base image.

hope that makes sense,
chris hunter


On 02/09/2015 10:08 AM, Chris Burroughs wrote:
> You could change the location of all modules with modpython.conf, but
> I'm not sure there is a way to add multiple locations to the search path.
>
> What is the problem you are running into with one directory?  I've
> usually had success with having $INSERT_CONFIG_MNGMT_TOOL drop in
> additional files.
>
> On 02/06/2015 04:37 PM, Yale Connect wrote:
>> Is there best practices for separating custom/contrib gmond python
>> modules from the packaged ones ?
>> Currently I have to install everything under lib64 (ie.
>> /usr/lib64/libganglia/python_modules) on our redhat boxes. It would be
>> easier to do sysadmin tasks if the custom ones had a different location
>> or easy to identify based on filename.
>>
>> regards,
>> chris hunter
>> yale hpc group
>>
>> On 02/05/2015 11:21 AM, Chris Burroughs wrote:
>>   > Currently python modules are bundled in monitor-core, some are in
>>   > gmond_python_modules (or os specific repos), and a few are in both.
>>   >
>>   > Ones in  monitor-core (at least in RedHat-land) get their own package
>>   > which makes them easy to install.  I suspect they are also
>> presumed to
>>   > by users to be somehow more 'official' or at least that's how I
>> thought
>>   > of them.  I don't think gmond_python_modules has releases or os
>>   > packaging for example.  I suspect some of this might reflect a
>> pre-git
>>   > situation where it was harder to contribute to monitoring-core.
>>   >
>>   > I'd like to propose the following for now:
>>   >    * For modules that are in both monitor-core and somewhere else,
>> make
>>   > the monitor-core version canonical and remove the other.
>>   >    * Everything else stays where it is.
>>   >
>>   > This will make it for to contribute patches are report issues without
>>   > looking in two different places and manually syncing files.
>>   >
>>   > Longer term there is probably something fancy we could do such as
>> build
>>   > time flags to opt modules in, or maybe switch to a deb/rpm per
>> module.
>>   > That way 'is this module "good enough"' can be decoupled from
>> which repo
>>   > is it in.
>>
>> ------------------------------------------------------------------------------
>>
>> Dive into the World of Parallel Programming. The Go Parallel Website,
>> sponsored by Intel and developed in partnership with Slashdot Media,
>> is your
>> hub for all things parallel software development, from weekly thought
>> leadership blogs to news, videos, case studies, tutorials and more.
>> Take a
>> look and join the conversation now.
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__goparallel.sourceforge.net_&d=AwICaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=d_G2h_sZYG4xtHMeKo8QgjDmOcMVdQvYgM-5Dri1AOY&m=QwGTadzrZoPu2F09ytAfA9WOFwhwdT7ecAAzhkPJXcE&s=gdxlpGW_jPrA6TLR8Hg13CII-3eG6gPSNV8t8GA_whk&e=
>> _______________________________________________
>> Ganglia-developers mailing list
>> Ganglia-developers@lists.sourceforge.net
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_ganglia-2Ddevelopers&d=AwICaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=d_G2h_sZYG4xtHMeKo8QgjDmOcMVdQvYgM-5Dri1AOY&m=QwGTadzrZoPu2F09ytAfA9WOFwhwdT7ecAAzhkPJXcE&s=ZCzzH4VIZ-oKhK2RFV0GkhdYC6hFmpHcF7MSI5G5Hiw&e=
>>
>

------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers

Reply via email to