[StarCluster] Setting environment variables across a cluster
    Justin Riley 
    jtriley at MIT.EDU
       
    Thu Aug  9 15:34:09 EDT 2012
    
    
  
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Chris,
My apologies for the long delay on this. Currently the easiest way to
do this is via a plugin that iterates through all the nodes and adds
entries to a file in /etc/profile.d (e.g. /etc/profile.d/scenv.sh).
Your environment would then be loaded anytime /etc/profile is sourced.
Here's an example of a simple plugin that would do this (untested):
https://gist.github.com/3307331
I'm working on adding the ability to specify a user data script for
all of the nodes so that scripts can be automatically run on node
start-up independent of StarCluster. Once this feature is added you
could create a simple bash/python/perl/etc script to do this, and any
other simple tasks, as soon as the instance boots...
HTH,
~Justin
On 07/23/2012 03:09 PM, Chris Diehl wrote:
> Hi All,
> 
> What is the most expedient way to set environment variables on all
> the nodes of a given cluster? I'd like to set PYTHONPATH on all of
> the nodes of a cluster after I fire it up.
> 
> Thanks, Chris _______________________________________________ 
> StarCluster mailing list StarCluster at mit.edu 
> http://mailman.mit.edu/mailman/listinfo/starcluster
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlAkELEACgkQ4llAkMfDcrkLCQCdFCi4V6lraS2FyT8US1AbQK7G
XWwAn2z6gz2Bq3h/ERMQ5Ef1UuA7Fyad
=YIrn
-----END PGP SIGNATURE-----
    
    
More information about the StarCluster
mailing list