> On Jan 6, 2016, at 8:38 PM, Christopher Samuel <[email protected]> wrote: > > > On 07/01/16 14:09, Ralph Castain wrote: > >> That is true, Chris - but the SLURM PMI implementations are all GPL 2.0. > > But Slurm is only one implementation of PMI, the MPICH FAQ says: > > https://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_What_are_process_managers.3F > > # These process managers communicate with MPICH processes using > # a predefined interface called as PMI (process management interface). > # Since the interface is (informally) standardized within MPICH and > # its derivatives, you can use any process manager from MPICH or its > # derivatives with any MPI application built with MPICH or any of its > # derivatives, as long as they follow the same wire protocol. There > # are three known implementations of the PMI wire protocol: "simple", > # "smpd" and "slurm". By default, MPICH and all its derivatives use > # the "simple" PMI wire protocol, but MPICH can be configured to use > # "smpd" or "slurm" as well. > > and perhaps more tellingly: > > # SLURM is an external process manager that uses MPICH's PMI interface > # as well. > > Given that and the fact that smpd and hydra is/was/are distributed in > MPICH under a BSD style permissive license I don't think there's > anything to worry about.
No offense, and IANAL, but I fear you are incorrect. Note that I’m talking strictly about launch via srun using the SLURM PMI support, not mpiexec. However, we can take this offline and stop spanning the list with this discussion if you like. Believe me - this has been a long-running point of discussion spanning the last 10 years and involving multiple legal depts. Suffice to say that it has been analyzed to death. :-( > > All the best, > Chris > -- > Christopher Samuel Senior Systems Administrator > VLSCI - Victorian Life Sciences Computation Initiative > Email: [email protected] Phone: +61 (0)3 903 55545 > http://www.vlsci.org.au/ http://twitter.com/vlsci
