[OMPI devel] OpenGrok (?)

2016-10-19 Thread Gilles Gouaillardet 
Folks,

OpenGrok (https;//svn.open-mpi.org/source) is no more accessible.
Is it an intermittent issue ? or did we simply forget to migrate it from UI ?

Config was not really up-to-date (master, v1.8 and obsolete versions
iirc) but i found it extremely useful (at least to search info on
master) and uses it quite a lot, both from my workstation and tablet

requirements can be found at http://opengrok.github.io/OpenGrok/ (and
there are some...), so if
migration is feasible, let me know if i can help

Cheers,

Gilles
___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Re: [OMPI devel] OpenGrok (?)

2016-10-19 Thread Jeff Squyres (jsquyres) 
Oh crud, I totally forgot that IU was running running OpenGrok.

I migrated Trac from IU to our AWS instance over the weekend, and updated the 
DNS name svn.open-mpi.org accordingly.  Hence, it's now pointing at AWS instead 
of IU, and we don't have OpenGrok running on the AWS instance.

We *can* run OpenGrok on our AWS instance, but it's one more thing that we as a 
community have to maintain.

What kinds of things do you use OpenGrok for?  Can you use the search bar at 
Github, instead?  (the github search bar can find types and functions in the 
code base, etc.)



> On Oct 19, 2016, at 7:30 AM, Gilles Gouaillardet 
>  wrote:
> 
> Folks,
> 
> OpenGrok (https;//svn.open-mpi.org/source) is no more accessible.
> Is it an intermittent issue ? or did we simply forget to migrate it from UI ?
> 
> Config was not really up-to-date (master, v1.8 and obsolete versions
> iirc) but i found it extremely useful (at least to search info on
> master) and uses it quite a lot, both from my workstation and tablet
> 
> requirements can be found at http://opengrok.github.io/OpenGrok/ (and
> there are some...), so if
> migration is feasible, let me know if i can help
> 
> Cheers,
> 
> Gilles
> ___
> devel mailing list
> devel@lists.open-mpi.org
> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Re: [OMPI devel] OpenGrok (?)

2016-10-19 Thread Gilles Gouaillardet 
Jeff,

The github search is basically a plain grep in the source code.

With OpenGrok, you can directly go to the definition.
When used to browse source code, types and functions are http links, so it
is really easy to follow the code.
OpenGrok can restrict the search to a specific path
(and the first "directory" is related to the branch)

Last but not least, OpenGrok can search for symbols
(for example search for 'bar' does not return anything for 'foobar')

Bottom line, OpenGrok is way more usable than the GitHub search bar

Cheers,

Gilles

On Wednesday, October 19, 2016, Jeff Squyres (jsquyres) 
wrote:

> Oh crud, I totally forgot that IU was running running OpenGrok.
>
> I migrated Trac from IU to our AWS instance over the weekend, and updated
> the DNS name svn.open-mpi.org accordingly.  Hence, it's now pointing at
> AWS instead of IU, and we don't have OpenGrok running on the AWS instance.
>
> We *can* run OpenGrok on our AWS instance, but it's one more thing that we
> as a community have to maintain.
>
> What kinds of things do you use OpenGrok for?  Can you use the search bar
> at Github, instead?  (the github search bar can find types and functions in
> the code base, etc.)
>
>
>
> > On Oct 19, 2016, at 7:30 AM, Gilles Gouaillardet <
> gilles.gouaillar...@gmail.com > wrote:
> >
> > Folks,
> >
> > OpenGrok (https;//svn.open-mpi.org/source) is no more accessible.
> > Is it an intermittent issue ? or did we simply forget to migrate it from
> UI ?
> >
> > Config was not really up-to-date (master, v1.8 and obsolete versions
> > iirc) but i found it extremely useful (at least to search info on
> > master) and uses it quite a lot, both from my workstation and tablet
> >
> > requirements can be found at http://opengrok.github.io/OpenGrok/ (and
> > there are some...), so if
> > migration is feasible, let me know if i can help
> >
> > Cheers,
> >
> > Gilles
> > ___
> > devel mailing list
> > devel@lists.open-mpi.org 
> > https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>
>
> --
> Jeff Squyres
> jsquy...@cisco.com 
> For corporate legal information go to: http://www.cisco.com/web/
> about/doing_business/legal/cri/
>
> ___
> devel mailing list
> devel@lists.open-mpi.org 
> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>
___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Re: [OMPI devel] MTT Server Downtime - Fri., Oct. 21, 2016 (Updated)

2016-10-19 Thread Josh Hursey 
Based on current estimates we need to extend the window of downtime for MTT
to 24 hours.

*Start time*: *Fri., Oct. 21, 2016 at Noon US Eastern* (11 am US Central)
*End time*: *Sat., Oct. 22, 2016 at Noon US Eastern* (estimated)

I will send an email just before taking down the MTT site on Friday, and
another once it is back up on Sat.

During this time all of the MTT services will be down - MTT Reporter and
MTT submission interface. If you have an MTT client running during this
time you will receive an error message if you try to submit results to the
MTT server.

Let me know if you have any questions or concerns.


On Tue, Oct 18, 2016 at 10:59 AM, Josh Hursey  wrote:

> We are moving this downtime to *Friday, Oct. 21 from 2-5 pm US Eastern*.
>
> We hit a snag with the AWS configuration that we are working through.
>
> On Sun, Oct 16, 2016 at 9:53 AM, Josh Hursey 
> wrote:
>
>> I will announce this on the Open MPI developer's teleconf on Tuesday,
>> before the move.
>>
>> Geoff - Please add this item to the agenda.
>>
>>
>> Short version:
>> ---
>> MTT server (mtt.open-mpi.org) will be going down for maintenance on
>> Tuesday, Oct. 18, 2016 from 2-5 pm US Eastern. During this time the MTT
>> Reporter and the MTT client submission interface will not be accessible. I
>> will send an email out when the service is back online.
>>
>>
>> Longer version:
>> ---
>> We need to move the MTT Server/Database from the IU server to the AWS
>> server. This move will be completely transparent to users submitting to the
>> database, except for a window of downtime to move the database.
>>
>> I estimate that moving the database will take about two hours. So I have
>> blocked off three hours to give us time to test, and redirect the DNS
>> record.
>>
>> Once the service comes back online, you should be able to access MTT
>> using themtt.open-mpi.org URL. No changes are needed in your MTT client
>> setup, and all permalinks are expected to still work after the move.
>>
>>
>> Let me know if you have any questions or concerns about the move.
>>
>>
>> --
>> Josh Hursey
>> IBM Spectrum MPI Developer
>>
>
>
>
> --
> Josh Hursey
> IBM Spectrum MPI Developer
>



-- 
Josh Hursey
IBM Spectrum MPI Developer
___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Re: [OMPI devel] OpenGrok (?)

2016-10-19 Thread Pritchard Jr., Howard 
Hi Jeff,

I’m not using it.

Howard

-- 
Howard Pritchard

HPC-DES
Los Alamos National Laboratory





On 10/19/16, 9:21 AM, "devel on behalf of Jeff Squyres (jsquyres)"
 wrote:

>Looking through the OpenGrok requirements, I have to admit that I'm not
>excited about running and maintaining a Tomcat server, the additional
>Java requirements, ...etc.  :-(
>
>Are there other people using OpenGrok?
>
>Are there alternative tools that we could use instead -- e.g., a
>cloud-hosted one that we can just point them to our git repo?  Or
>something that can run locally for individual developers?
>
>
>
>> On Oct 19, 2016, at 10:37 AM, Gilles Gouaillardet
>> wrote:
>> 
>> Jeff,
>> 
>> The github search is basically a plain grep in the source code.
>> 
>> With OpenGrok, you can directly go to the definition.
>> When used to browse source code, types and functions are http links, so
>>it is really easy to follow the code.
>> OpenGrok can restrict the search to a specific path
>> (and the first "directory" is related to the branch)
>> 
>> Last but not least, OpenGrok can search for symbols
>> (for example search for 'bar' does not return anything for 'foobar')
>> 
>> Bottom line, OpenGrok is way more usable than the GitHub search bar
>> 
>> Cheers,
>> 
>> Gilles
>> 
>> On Wednesday, October 19, 2016, Jeff Squyres (jsquyres)
>> wrote:
>> Oh crud, I totally forgot that IU was running running OpenGrok.
>> 
>> I migrated Trac from IU to our AWS instance over the weekend, and
>>updated the DNS name svn.open-mpi.org accordingly.  Hence, it's now
>>pointing at AWS instead of IU, and we don't have OpenGrok running on the
>>AWS instance.
>> 
>> We *can* run OpenGrok on our AWS instance, but it's one more thing that
>>we as a community have to maintain.
>> 
>> What kinds of things do you use OpenGrok for?  Can you use the search
>>bar at Github, instead?  (the github search bar can find types and
>>functions in the code base, etc.)
>> 
>> 
>> 
>> > On Oct 19, 2016, at 7:30 AM, Gilles Gouaillardet
>> wrote:
>> >
>> > Folks,
>> >
>> > OpenGrok (https;//svn.open-mpi.org/source) is no more accessible.
>> > Is it an intermittent issue ? or did we simply forget to migrate it
>>from UI ?
>> >
>> > Config was not really up-to-date (master, v1.8 and obsolete versions
>> > iirc) but i found it extremely useful (at least to search info on
>> > master) and uses it quite a lot, both from my workstation and tablet
>> >
>> > requirements can be found at http://opengrok.github.io/OpenGrok/ (and
>> > there are some...), so if
>> > migration is feasible, let me know if i can help
>> >
>> > Cheers,
>> >
>> > Gilles
>> > ___
>> > devel mailing list
>> > devel@lists.open-mpi.org
>> > https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>> 
>> 
>> --
>> Jeff Squyres
>> jsquy...@cisco.com
>> For corporate legal information go to:
>>http://www.cisco.com/web/about/doing_business/legal/cri/
>> 
>> ___
>> devel mailing list
>> devel@lists.open-mpi.org
>> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>> ___
>> devel mailing list
>> devel@lists.open-mpi.org
>> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>
>
>-- 
>Jeff Squyres
>jsquy...@cisco.com
>For corporate legal information go to:
>http://www.cisco.com/web/about/doing_business/legal/cri/
>
>___
>devel mailing list
>devel@lists.open-mpi.org
>https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Re: [OMPI devel] OpenGrok (?)

2016-10-19 Thread Jeff Squyres (jsquyres) 
Looking through the OpenGrok requirements, I have to admit that I'm not excited 
about running and maintaining a Tomcat server, the additional Java 
requirements, ...etc.  :-(

Are there other people using OpenGrok?

Are there alternative tools that we could use instead -- e.g., a cloud-hosted 
one that we can just point them to our git repo?  Or something that can run 
locally for individual developers?



> On Oct 19, 2016, at 10:37 AM, Gilles Gouaillardet 
>  wrote:
> 
> Jeff,
> 
> The github search is basically a plain grep in the source code.
> 
> With OpenGrok, you can directly go to the definition.
> When used to browse source code, types and functions are http links, so it is 
> really easy to follow the code.
> OpenGrok can restrict the search to a specific path
> (and the first "directory" is related to the branch)
> 
> Last but not least, OpenGrok can search for symbols
> (for example search for 'bar' does not return anything for 'foobar')
> 
> Bottom line, OpenGrok is way more usable than the GitHub search bar
> 
> Cheers,
> 
> Gilles
> 
> On Wednesday, October 19, 2016, Jeff Squyres (jsquyres)  
> wrote:
> Oh crud, I totally forgot that IU was running running OpenGrok.
> 
> I migrated Trac from IU to our AWS instance over the weekend, and updated the 
> DNS name svn.open-mpi.org accordingly.  Hence, it's now pointing at AWS 
> instead of IU, and we don't have OpenGrok running on the AWS instance.
> 
> We *can* run OpenGrok on our AWS instance, but it's one more thing that we as 
> a community have to maintain.
> 
> What kinds of things do you use OpenGrok for?  Can you use the search bar at 
> Github, instead?  (the github search bar can find types and functions in the 
> code base, etc.)
> 
> 
> 
> > On Oct 19, 2016, at 7:30 AM, Gilles Gouaillardet 
> >  wrote:
> >
> > Folks,
> >
> > OpenGrok (https;//svn.open-mpi.org/source) is no more accessible.
> > Is it an intermittent issue ? or did we simply forget to migrate it from UI 
> > ?
> >
> > Config was not really up-to-date (master, v1.8 and obsolete versions
> > iirc) but i found it extremely useful (at least to search info on
> > master) and uses it quite a lot, both from my workstation and tablet
> >
> > requirements can be found at http://opengrok.github.io/OpenGrok/ (and
> > there are some...), so if
> > migration is feasible, let me know if i can help
> >
> > Cheers,
> >
> > Gilles
> > ___
> > devel mailing list
> > devel@lists.open-mpi.org
> > https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
> 
> 
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to: 
> http://www.cisco.com/web/about/doing_business/legal/cri/
> 
> ___
> devel mailing list
> devel@lists.open-mpi.org
> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
> ___
> devel mailing list
> devel@lists.open-mpi.org
> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel

Re: [OMPI devel] Fwd: Problem with double shared library

2016-10-19 Thread Jeff Squyres (jsquyres) 
The reasons for this was so that the plugins do not have to be dependent upon a 
specific version of Open MPI (or, even more restrictive, a specific tuple of 
Open MPI libraries). This allows third parties to distribute binary plugins 
that work with multiple versions of open MPI.

Sent from my phone. No type good.

On Oct 17, 2016, at 9:49 PM, Gilles Gouaillardet 
mailto:gil...@rist.or.jp>> wrote:


Folks,


this is a follow up on a question from the users ML


is there any reason why plugins do not depend on the main openmpi libs 
(libopen-pal.so and libopen-rte.so, libompi.so and liboshmem.so if needed) ?

i guess that would solve the issue here without having to use RTLD_GLOBAL.


Cheers,


Gilles


 Forwarded Message 
Subject:Re: [OMPI users] Problem with double shared library
Date:   Tue, 18 Oct 2016 10:45:42 +0900
From:   Gilles Gouaillardet 
To: Open MPI Users 




Sean,


if i understand correctly, your built a libtransport_mpi.so library that 
depends on Open MPI, and your main program dlopen libtransport_mpi.so.

in this case, and at least for the time being,  you need to use RTLD_GLOBAL in 
your dlopen flags.


Cheers,


Gilles

On 10/18/2016 4:53 AM, Sean Ahern wrote:
Folks,

For our code, we have a communication layer that abstracts the code that does 
the actual transfer of data. We call these "transports", and we link them as 
shared libraries. We have created an MPI transport that compiles/links against 
OpenMPI 2.0.1 using the compiler wrappers. When I compile OpenMPI with 
the--disable-dlopen option (thus cramming all of OpenMPI's plugins into the MPI 
library directly), things work great with our transport shared library. But 
when I have a "normal" OpenMPI (without --disable-dlopen) and create the same 
transport shared library, things fail. Upon launch, it appears that OpenMPI is 
unable to find the appropriate plugins:

[hyperion.ceintl.com:25595] 
mca_base_component_repository_open: unable to open mca_patcher_overwrite: 
/home/sean/work/ceisvn/apex/branches/OpenMPI/apex32/machines/linux_2.6_64/openmpi-2.0.1/lib/openmpi/mca_patcher_overwrite.so:
 undefined symbol: mca_patcher_base_patch_t_class (ignored)
[hyperion.ceintl.com:25595] 
mca_base_component_repository_open: unable to open mca_shmem_mmap: 
/home/sean/work/ceisvn/apex/branches/OpenMPI/apex32/machines/linux_2.6_64/openmpi-2.0.1/lib/openmpi/mca_shmem_mmap.so:
 undefined symbol: opal_show_help (ignored)
[hyperion.ceintl.com:25595] 
mca_base_component_repository_open: unable to open mca_shmem_posix: 
/home/sean/work/ceisvn/apex/branches/OpenMPI/apex32/machines/linux_2.6_64/openmpi-2.0.1/lib/openmpi/mca_shmem_posix.so:
 undefined symbol: opal_show_help (ignored)
[hyperion.ceintl.com:25595] 
mca_base_component_repository_open: unable to open mca_shmem_sysv: 
/home/sean/work/ceisvn/apex/branches/OpenMPI/apex32/machines/linux_2.6_64/openmpi-2.0.1/lib/openmpi/mca_shmem_sysv.so:
 undefined symbol: opal_show_help (ignored)
--
It looks like opal_init failed for some reason; your parallel process is
likely to abort.  There are many reasons that a parallel process can
fail during opal_init; some of which are due to configuration or
environment problems.  This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):

  opal_shmem_base_select failed
  --> Returned value -1 instead of OPAL_SUCCESS
--
--
It looks like orte_init failed for some reason; your parallel process is
likely to abort.  There are many reasons that a parallel process can
fail during orte_init; some of which are due to configuration or
environment problems.  This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):

  opal_init failed
  --> Returned value Error (-1) instead of ORTE_SUCCESS
--
--
It looks like MPI_INIT failed for some reason; your parallel process is
likely to abort.  There are many reasons that a parallel process can
fail during MPI_INIT; some of which are due to configuration or environment
problems.  This failure appears to be an internal failure; here's some
additional information (which may only be relevant to an Open MPI
developer):

  ompi_mpi_init: ompi_rte_init failed
  --> Returned "Error" (-1) instead of "Success" (0)

If I skip our shared libraries and instead write a standard MPI-based "hello, 
world" program that lin

Re: [OMPI devel] OMPI devel] Fwd: Problem with double shared library

2016-10-19 Thread Gilles Gouaillardet 
Thanks Jeff !

Gilles

"Jeff Squyres (jsquyres)"  wrote:
>The reasons for this was so that the plugins do not have to be dependent upon 
>a specific version of Open MPI (or, even more restrictive, a specific tuple of 
>Open MPI libraries). This allows third parties to distribute binary plugins 
>that work with multiple versions of open MPI. 
>
>Sent from my phone. No type good. 
>
>
>On Oct 17, 2016, at 9:49 PM, Gilles Gouaillardet  wrote:
>
>Folks,
>
>
>this is a follow up on a question from the users ML
>
>
>is there any reason why plugins do not depend on the main openmpi libs 
>(libopen-pal.so and libopen-rte.so, libompi.so and liboshmem.so if needed) ?
>
>i guess that would solve the issue here without having to use RTLD_GLOBAL.
>
>
>Cheers,
>
>
>Gilles
>
>
>
> Forwarded Message  Subject: Re: [OMPI users] Problem with 
>double shared libraryDate: Tue, 18 Oct 2016 10:45:42 +0900From: Gilles 
>Gouaillardet To: Open MPI Users  
>
>Sean,
>
>
>if i understand correctly, your built a libtransport_mpi.so library that 
>depends on Open MPI, and your main program dlopen libtransport_mpi.so.
>
>in this case, and at least for the time being,  you need to use RTLD_GLOBAL in 
>your dlopen flags.
>
>
>Cheers,
>
>
>Gilles
>
>
>On 10/18/2016 4:53 AM, Sean Ahern wrote:
>
>Folks,
>
>
>For our code, we have a communication layer that abstracts the code that does 
>the actual transfer of data. We call these "transports", and we link them as 
>shared libraries. We have created an MPI transport that compiles/links against 
>OpenMPI 2.0.1 using the compiler wrappers. When I compile OpenMPI with 
>the--disable-dlopen option (thus cramming all of OpenMPI's plugins into the 
>MPI library directly), things work great with our transport shared library. 
>But when I have a "normal" OpenMPI (without --disable-dlopen) and create the 
>same transport shared library, things fail. Upon launch, it appears that 
>OpenMPI is unable to find the appropriate plugins:
>
>
>[hyperion.ceintl.com:25595] mca_base_component_repository_open: unable to open 
>mca_patcher_overwrite: 
>/home/sean/work/ceisvn/apex/branches/OpenMPI/apex32/machines/linux_2.6_64/openmpi-2.0.1/lib/openmpi/mca_patcher_overwrite.so:
> undefined symbol: mca_patcher_base_patch_t_class (ignored)
>
>[hyperion.ceintl.com:25595] mca_base_component_repository_open: unable to open 
>mca_shmem_mmap: 
>/home/sean/work/ceisvn/apex/branches/OpenMPI/apex32/machines/linux_2.6_64/openmpi-2.0.1/lib/openmpi/mca_shmem_mmap.so:
> undefined symbol: opal_show_help (ignored)
>
>[hyperion.ceintl.com:25595] mca_base_component_repository_open: unable to open 
>mca_shmem_posix: 
>/home/sean/work/ceisvn/apex/branches/OpenMPI/apex32/machines/linux_2.6_64/openmpi-2.0.1/lib/openmpi/mca_shmem_posix.so:
> undefined symbol: opal_show_help (ignored)
>
>[hyperion.ceintl.com:25595] mca_base_component_repository_open: unable to open 
>mca_shmem_sysv: 
>/home/sean/work/ceisvn/apex/branches/OpenMPI/apex32/machines/linux_2.6_64/openmpi-2.0.1/lib/openmpi/mca_shmem_sysv.so:
> undefined symbol: opal_show_help (ignored)
>
>--
>
>It looks like opal_init failed for some reason; your parallel process is
>
>likely to abort.  There are many reasons that a parallel process can
>
>fail during opal_init; some of which are due to configuration or
>
>environment problems.  This failure appears to be an internal failure;
>
>here's some additional information (which may only be relevant to an
>
>Open MPI developer):
>
>
>  opal_shmem_base_select failed
>
>  --> Returned value -1 instead of OPAL_SUCCESS
>
>--
>
>--
>
>It looks like orte_init failed for some reason; your parallel process is
>
>likely to abort.  There are many reasons that a parallel process can
>
>fail during orte_init; some of which are due to configuration or
>
>environment problems.  This failure appears to be an internal failure;
>
>here's some additional information (which may only be relevant to an
>
>Open MPI developer):
>
>
>  opal_init failed
>
>  --> Returned value Error (-1) instead of ORTE_SUCCESS
>
>--
>
>--
>
>It looks like MPI_INIT failed for some reason; your parallel process is
>
>likely to abort.  There are many reasons that a parallel process can
>
>fail during MPI_INIT; some of which are due to configuration or environment
>
>problems.  This failure appears to be an internal failure; here's some
>
>additional information (which may only be relevant to an Open MPI
>
>developer):
>
>
>  ompi_mpi_init: ompi_rte_init failed
>
>  --> Returned "Error" (-1) instead of "Success" (0)
>
>
>If I skip our shared libraries and instead write a standard MPI-based "hello, 
>world" program th