11 Jan
2023
11 Jan
'23
1:23 p.m.
On Wed, Jan 11, 2023 at 7:44 AM Yehuda Sadeh-Weinraub <yehuda(a)redhat.com> wrote:
I
On Tue, Jan 10, 2023, 8:38 PM Gregory Farnum <gfarnum(a)redhat.com> wrote:
+1
Let's disable it for now and wait for confirmation before removing it entirely.
--
Cheers,
Venky
Hi all,
As you all know, we’ve had a lot of issues in sepia recently. One of them is that we’re
having trouble with Java paths during builds (I havent followed the details, tbh). Radek
pointed out [1] that CephFS seems to be the only user of Java in the codebase, and when I
ran a “git grep” the only occurrences were for cephfs-java, which AFAIK only exists to
support the (very defunct) Hadoop plug-in.
Are there no other users? Can we disable this temporarily to get builds working in the
lab and continue testing? Is anybody going to notice if we remove it?
If the answers are “yes”, let’s do as much as we can and get some builds going ASAP?
Why not go ahead with disabling it now for the sake of testing, while figuring out
whether we actually need/want it? 
11 Jan
11 Jan
1:45 p.m.
New subject: [ceph-fs-team] Java usage in Ceph
https://github.com/ceph/ceph/pull/49711 seems like it will suffice.
-Sam
On Tue, Jan 10, 2023 at 8:24 PM Venky Shankar <vshankar(a)redhat.com> wrote:
On Wed, Jan 11, 2023 at 7:44 AM Yehuda Sadeh-Weinraub <yehuda(a)redhat.com> wrote:
I
On Tue, Jan 10, 2023, 8:38 PM Gregory Farnum <gfarnum(a)redhat.com> wrote:
+1
Let's disable it for now and wait for confirmation before removing it entirely.
--
Cheers,
Venky
_______________________________________________
Dev mailing list -- dev(a)ceph.io
To unsubscribe send an email to dev-leave(a)ceph.io
Hi all,
As you all know, we’ve had a lot of issues in sepia recently. One of them is that we’re
having trouble with Java paths during builds (I havent followed the details, tbh). Radek
pointed out [1] that CephFS seems to be the only user of Java in the codebase, and when I
ran a “git grep” the only occurrences were for cephfs-java, which AFAIK only exists to
support the (very defunct) Hadoop plug-in.
Are there no other users? Can we disable this temporarily to get builds working in the
lab and continue testing? Is anybody going to notice if we remove it?
If the answers are “yes”, let’s do as much as we can and get some builds going ASAP?
Why not go ahead with disabling it now for the sake of testing, while figuring out
whether we actually need/want it? 
6:15 p.m.
New subject: [ceph-fs-team] Java usage in Ceph
FWIW, I think I've resolved the java issue on the centos8 builders. I
don't know why installing v352 of the jdk didn't also update the
-headless package, but manually removing the latter and then
reinstalling the former on all the slaves got everything synced. It's
still building, but I think
https://jenkins.ceph.com/job/ceph-dev-new-build/67239/ARCH=x86_64,AVAILABLE…
will show success with a "dummy commit on top of main" branch.
On 1/10/2023 8:45 PM, Sam Just wrote:
https://github.com/ceph/ceph/pull/49711 seems like it
will suffice.
-Sam
On Tue, Jan 10, 2023 at 8:24 PM Venky Shankar <vshankar(a)redhat.com> wrote:
On Wed, Jan 11, 2023 at 7:44 AM Yehuda Sadeh-Weinraub <yehuda(a)redhat.com> wrote:
_______________________________________________
Sepia mailing list -- sepia(a)ceph.io
To unsubscribe send an email to sepia-leave(a)ceph.io
I
On Tue, Jan 10, 2023, 8:38 PM Gregory Farnum <gfarnum(a)redhat.com> wrote:
+1
Let's disable it for now and wait for confirmation before removing it entirely.
--
Cheers,
Venky
_______________________________________________
Dev mailing list -- dev(a)ceph.io
To unsubscribe send an email to dev-leave(a)ceph.io
Hi all,
As you all know, we’ve had a lot of issues in sepia recently. One of them is that we’re
having trouble with Java paths during builds (I havent followed the details, tbh). Radek
pointed out [1] that CephFS seems to be the only user of Java in the codebase, and when I
ran a “git grep” the only occurrences were for cephfs-java, which AFAIK only exists to
support the (very defunct) Hadoop plug-in.
Are there no other users? Can we disable this temporarily to get builds working in the
lab and continue testing? Is anybody going to notice if we remove it?
If the answers are “yes”, let’s do as much as we can and get some builds going ASAP?
Why not go ahead with disabling it now for the sake of testing, while figuring out
whether we actually need/want it?
473
days inactive
473
days old
2 comments
3 participants
participants (3)
-
Dan Mick -
Sam Just -
Venky Shankar