RFC: Splitting of the management git tree in Open Fabrics

RFC: Splitting of the management git tree in Open Fabrics

[Ira Weiny]

As I briefly mentioned in an email to Yevgeny regarding libibumad ABI's; I
believe it is time to break up the management git tree.

With GA of OFED 1.5.2 scheduled for Sept 13, I would like to request comments
from the community about the following split after that GA.

On openfabrics.org/git split management.git into the following trees.

openfabrics.org/git/infiniband-diags.git
openfabrics.org/git/libibumad.git
openfabrics.org/git/libibmad.git
openfabrics.org/git/opensm.git
 
Sasha can populate those from the current management tree.  We believe there
are git commands which will do this without losing any history from the git
trees.

Vlad, what changes would you have to make in the OFED build to accommodate
these packages being in separate git trees?

Any other concerns or comments?

Thanks,
Ira

-- 
Ira Weiny
Math Programmer/Computer Scientist
Lawrence Livermore National Lab
925-423-8008
weiny2-i2BcT+NCU+M@public.gmane.org

Re: RFC: Splitting of the management git tree in Open Fabrics

[Vladimir Sokolovsky]

On 08/31/2010 10:51 PM, Ira Weiny wrote:
> As I briefly mentioned in an email to Yevgeny regarding libibumad ABI's; I
> believe it is time to break up the management git tree.
>
> With GA of OFED 1.5.2 scheduled for Sept 13, I would like to request comments
> from the community about the following split after that GA.
>
> On openfabrics.org/git split management.git into the following trees.
>
> openfabrics.org/git/infiniband-diags.git
> openfabrics.org/git/libibumad.git
> openfabrics.org/git/libibmad.git
> openfabrics.org/git/opensm.git
>
> Sasha can populate those from the current management tree.  We believe there
> are git commands which will do this without losing any history from the git
> trees.
>
> Vlad, what changes would you have to make in the OFED build to accommodate
> these packages being in separate git trees?
>

No changes will be required to the OFED build as all management packages are
taken as tarballs from http://www.openfabrics.org/downloads/management

Regards,
Vladimir

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Splitting of the management git tree in Open Fabrics

[Hefty, Sean]

> With GA of OFED 1.5.2 scheduled for Sept 13, I would like to request
> comments
> from the community about the following split after that GA.
> 
> On openfabrics.org/git split management.git into the following trees.
> 
> openfabrics.org/git/infiniband-diags.git
> openfabrics.org/git/libibumad.git
> openfabrics.org/git/libibmad.git
> openfabrics.org/git/opensm.git

I think this makes sense.  Not sure that it would have any effect on the windows port, but nothing that I don't think couldn't be dealt with.  Are there any source files shared between the different components?

Re: RFC: Splitting of the management git tree in Open Fabrics

[Hal Rosenstock]

Ira,

On Tue, Aug 31, 2010 at 3:51 PM, Ira Weiny <weiny2-i2BcT+NCU+M@public.gmane.org> wrote:
> As I briefly mentioned in an email to Yevgeny regarding libibumad ABI's; I
> believe it is time to break up the management git tree.

I think these are separate issues. What are you trying to achieve by
doing this ?

-- Hal

> With GA of OFED 1.5.2 scheduled for Sept 13, I would like to request comments
> from the community about the following split after that GA.
>
> On openfabrics.org/git split management.git into the following trees.
>
> openfabrics.org/git/infiniband-diags.git
> openfabrics.org/git/libibumad.git
> openfabrics.org/git/libibmad.git
> openfabrics.org/git/opensm.git
>
> Sasha can populate those from the current management tree.  We believe there
> are git commands which will do this without losing any history from the git
> trees.
>
> Vlad, what changes would you have to make in the OFED build to accommodate
> these packages being in separate git trees?
>
> Any other concerns or comments?
>
> Thanks,
> Ira
>
> --
> Ira Weiny
> Math Programmer/Computer Scientist
> Lawrence Livermore National Lab
> 925-423-8008
> weiny2-i2BcT+NCU+M@public.gmane.org
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: RFC: Splitting of the management git tree in Open Fabrics

[Ira Weiny]

On Thu, 2 Sep 2010 13:36:34 -0700
Hal Rosenstock <hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> Ira,
> 
> On Tue, Aug 31, 2010 at 3:51 PM, Ira Weiny <weiny2-i2BcT+NCU+M@public.gmane.org> wrote:
> > As I briefly mentioned in an email to Yevgeny regarding libibumad ABI's; I
> > believe it is time to break up the management git tree.
> 
> I think these are separate issues. What are you trying to achieve by
> doing this ?

Yes they are separate issues.  That is why I started this thread.

When I said "I think it is time to break up the management git tree" I was
thinking along the lines that umad and mad are libraries used by tools outside
of OpenSM and infiniband-diags.  As such I think it would be easier to
maintain them as separate trees.  This includes maintaining branches and
versions with consistent ABI's.

Ira

> 
> -- Hal
> 
> > With GA of OFED 1.5.2 scheduled for Sept 13, I would like to request comments
> > from the community about the following split after that GA.
> >
> > On openfabrics.org/git split management.git into the following trees.
> >
> > openfabrics.org/git/infiniband-diags.git
> > openfabrics.org/git/libibumad.git
> > openfabrics.org/git/libibmad.git
> > openfabrics.org/git/opensm.git
> >
> > Sasha can populate those from the current management tree.  We believe there
> > are git commands which will do this without losing any history from the git
> > trees.
> >
> > Vlad, what changes would you have to make in the OFED build to accommodate
> > these packages being in separate git trees?
> >
> > Any other concerns or comments?
> >
> > Thanks,
> > Ira
> >
> > --
> > Ira Weiny
> > Math Programmer/Computer Scientist
> > Lawrence Livermore National Lab
> > 925-423-8008
> > weiny2-i2BcT+NCU+M@public.gmane.org
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> > the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> > More majordomo info at  http://*vger.kernel.org/majordomo-info.html
> >
> 


-- 
Ira Weiny
Math Programmer/Computer Scientist
Lawrence Livermore National Lab
925-423-8008
weiny2-i2BcT+NCU+M@public.gmane.org

Re: RFC: Splitting of the management git tree in Open Fabrics

[Sasha Khapyorsky]

Hi,

On 12:51 Tue 31 Aug     , Ira Weiny wrote:
> 
> On openfabrics.org/git split management.git into the following trees.
> 
> openfabrics.org/git/infiniband-diags.git
> openfabrics.org/git/libibumad.git
> openfabrics.org/git/libibmad.git
> openfabrics.org/git/opensm.git
>  
> Sasha can populate those from the current management tree.  We believe there
> are git commands which will do this without losing any history from the git
> trees.

As was already discussed. I'm going to split management tree into
separate libibumad, libibmad, opensm and infiniband-diags trees and
will publish this soon (few days). The history will be preserved as per
sub-tree.

Sasha
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html