Re: Ceph license change

[Daniel P. Berrangé]

On Tue, Feb 04, 2020 at 01:01:24PM +0000, Sage Weil wrote:
>  On Tue, 4 Feb 2020, Kaleb Keithley wrote:
>  > On Mon, Feb 3, 2020 at 11:35 PM Daniel P. Berrangé <berrange(a)redhat.com&gt;
>  > wrote:
>  > 
>  > > On Mon, Feb 03, 2020 at 11:26:46PM +0530, Kaleb Keithley wrote:
>  > > > Coming in Ceph-15 (octopus)
>  > > >
>  > > > From: LGPL-2.1 and CC-BY-SA-3.0 and GPL-2.0 and BSL-1.0 and BSD-3-Clause
>  > > > and MIT
>  > > > To:      LGPL-2.1 and LGPL-3.0 and CC-BY-SA-3.0 and GPL-2.0 and BSL-1.0
>  > > and
>  > > > BSD-3-Clause and MIT
>  > >
>  > > Do you have info on which parts of Ceph are covered by the newly
>  > > introduced LGPLv3.0 ?
>  > >
>  > 
>  > Not off hand no. Maybe the new seastar bits?
>  > 
>  > Sage (cc'd) made the change to the upstream .spec file.  Sage?
>  
>  We changed from LGPL-2.1 to LGPL-2.1 or LGPL-3.0 in order to avoid 
>  ambiguity with Apache-2.0 compatibility (we use seastar).  See
>  
>  https://github.com/ceph/ceph/pull/22446
>  
>  FWIW none of the Apache-2.0 code affects the client library, so this 
>  should have no effect on programs linking to librados or librbd 
>  (like qemu), although the "or" is a blanket change across most of the 
>  code and not narrowly applied in that way. 
Just to be clear, can you confirm that librados/librbd will never link
to anything that is Apache 2.0 licensed, directly or indirectly ?

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|