You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Jason Gerlowski <ge...@apache.org> on 2024/06/25 18:20:35 UTC
lucene-solr-1 Jenkins Agent Management
Hey all,
Sending this email to discuss the ASF Jenkins' 'lucene-solr-1' worker
node, which both Lucene and Solr use to run builds.
While investigating a recent issue with some Solr builds, I asked
INFRA to restart 'lucene-solr-1'. They were happy to oblige (and I'm
now unblocked), but in the process they mentioned that 'lucene-solr-1'
was a "project run VM" and that someone in the project should have the
requisite access and permissions. [1] [2]
This was all a surprise to me, so I wanted to follow up here with a
few questions.
1. Is it true that our projects run or manage this VM in some way?
2. If so, does anyone remember the context around how or why this came
about? (As opposed to using one of the "standard" Jenkins build
machines that INFRA provides...)
3. Who all can access the box? How are credentials managed? (My
suspicion is that no one currently active on the Solr lists is able to
access the box, which seems worth remedying...)
Best,
Jason
[1] https://lists.apache.org/thread/g0y0ohczdctv0v5fn8sqv4t0j4y6hp68
[2] https://the-asf.slack.com/archives/CBX4TSBQ8/p1719318685682309
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: lucene-solr-1 Jenkins Agent Management
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi Jason,
Am 26.06.2024 um 16:30 schrieb Jason Gerlowski:
> Hi Uwe
>
> Thanks for the context! A few follow-up questions for you (or anyone
> else that can answer):
>
> 1. What's the hostname for lucene-solr-1? Maybe my Jenkins knowledge
> is lacking, but I can't find the full hostname exposed anywhere in
> Jenkins, and I'd like to try SSH-ing in. (I'm hoping it might "just
> work" as I have a SSH key set up through id.apache.org and am on the
> Lucene PMC.)
lucene-us-west.apache.org (I think this is the machine lucene-solr-2 in
Jenkins) and lucene1-us-west.apache.org (this seems to be
"lucene-solr-1" in jenkins"). I see this from "ps -fu jenkins" (it has
running gradle processes).
You may need to also sudo when you are on the machine. In that case you
need to use that strange 2 factor auth stuff. It is somewhere documented
at INFRA. Bascally when you sudo, it asks for a password and gives you
an otp-md5 challenge. You need to enter it together with your ASF
password here (https://selfserve.apache.org/otp-calculator.html) and
then copy the result into the sudo as password.
> 2. AFAICT from its page in Jenkins
> (https://ci-builds.apache.org/computer/lucene%2Dsolr%2D2/),
> lucene-solr-2 has been "down" for some time. Does anyone know why
> this is?
No idea, both machines are up and running. Both of them have a slave.jar
running.
This is something for INFRA to check. I killed the slave process now.
Maybe it recovers.
> 3. Is there a particular reason why we have project-managed VMs,
> instead of using INFRA-managed nodes?
That is because we wanted to have direct access to it, so we can place
the correct config files in the jenkins home directory with
randomization settings, number of CPUs and all other gradle goodies.
The machine is still maintained by INFRA (puppet,....) but we have
access. That's all.
> 4. You mention that the VMs are only owned by the Lucene PMC. Is that
> mostly a historical accident (i.e. because the Solr PMC didn't
> technically exist at the time the VMs were created)? Or is there some
> conceptual reason the VMs should continue to be owned by Lucene PMC
> only?
Yes, Solr PMC did not exist. As you see from the hostnames, it is
"lucene" and "lucene1"
>
> Best,
>
> Jason
>
> On Wed, Jun 26, 2024 at 5:30 AM Uwe Schindler <uw...@thetaphi.de> wrote:
>> Hi,
>>
>> yes e.g., I have access to that machine and can issue a reboot. The two
>> machines are VMs specifically owned by the Lucene PMC (not Solr as far
>> as I remeber), but they were created before the split of projects.
>>
>> Some people have direct access, not sure how this is managed. Basically
>> to get access you need to place a SSH key in id.apache.org -- and I
>> think you need to be in the correct PMC.
>>
>> P.S.: I sometimes also run "apt update && apt dist-upgrade" to keep it
>> uptodate (but not recently).
>>
>> Uwe
>>
>> Am 25.06.2024 um 20:20 schrieb Jason Gerlowski:
>>> Hey all,
>>>
>>> Sending this email to discuss the ASF Jenkins' 'lucene-solr-1' worker
>>> node, which both Lucene and Solr use to run builds.
>>>
>>> While investigating a recent issue with some Solr builds, I asked
>>> INFRA to restart 'lucene-solr-1'. They were happy to oblige (and I'm
>>> now unblocked), but in the process they mentioned that 'lucene-solr-1'
>>> was a "project run VM" and that someone in the project should have the
>>> requisite access and permissions. [1] [2]
>>>
>>> This was all a surprise to me, so I wanted to follow up here with a
>>> few questions.
>>>
>>> 1. Is it true that our projects run or manage this VM in some way?
>>> 2. If so, does anyone remember the context around how or why this came
>>> about? (As opposed to using one of the "standard" Jenkins build
>>> machines that INFRA provides...)
>>> 3. Who all can access the box? How are credentials managed? (My
>>> suspicion is that no one currently active on the Solr lists is able to
>>> access the box, which seems worth remedying...)
>>>
>>> Best,
>>>
>>> Jason
>>>
>>> [1] https://lists.apache.org/thread/g0y0ohczdctv0v5fn8sqv4t0j4y6hp68
>>> [2] https://the-asf.slack.com/archives/CBX4TSBQ8/p1719318685682309
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>> --
>> Uwe Schindler
>> Achterdiek 19, D-28357 Bremen
>> https://www.thetaphi.de
>> eMail: uwe@thetaphi.de
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: uwe@thetaphi.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: lucene-solr-1 Jenkins Agent Management
Posted by Dawid Weiss <da...@gmail.com>.
This is the page Uwe mentioned -
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=122916896
On Mon, Jul 1, 2024 at 5:51 PM Jason Gerlowski <ge...@gmail.com>
wrote:
> Thanks again Uwe!
>
> On Wed, Jun 26, 2024 at 4:41 PM Uwe Schindler <uw...@thetaphi.de> wrote:
> >
> > Sorry,
> >
> > it's dead again. So fixing the stuck slave is up to ASF INFRA. Maybe its
> > something like wrong Java version. Without any logfiles its impossible
> > to guess.
> >
> > Uwe
> >
> > Am 26.06.2024 um 22:39 schrieb Uwe Schindler:
> > > Hi,
> > >
> > > looks like killing the stuck slave process ("sudo pkill -9 -u
> > > jenkins") helped lucene-solr-2 to recover.
> > >
> > > Uwe
> > >
> > > Am 26.06.2024 um 16:30 schrieb Jason Gerlowski:
> > >> Hi Uwe
> > >>
> > >> Thanks for the context! A few follow-up questions for you (or anyone
> > >> else that can answer):
> > >>
> > >> 1. What's the hostname for lucene-solr-1? Maybe my Jenkins knowledge
> > >> is lacking, but I can't find the full hostname exposed anywhere in
> > >> Jenkins, and I'd like to try SSH-ing in. (I'm hoping it might "just
> > >> work" as I have a SSH key set up through id.apache.org and am on the
> > >> Lucene PMC.)
> > >> 2. AFAICT from its page in Jenkins
> > >> (https://ci-builds.apache.org/computer/lucene%2Dsolr%2D2/),
> > >> lucene-solr-2 has been "down" for some time. Does anyone know why
> > >> this is?
> > >> 3. Is there a particular reason why we have project-managed VMs,
> > >> instead of using INFRA-managed nodes?
> > >> 4. You mention that the VMs are only owned by the Lucene PMC. Is that
> > >> mostly a historical accident (i.e. because the Solr PMC didn't
> > >> technically exist at the time the VMs were created)? Or is there some
> > >> conceptual reason the VMs should continue to be owned by Lucene PMC
> > >> only?
> > >>
> > >> Best,
> > >>
> > >> Jason
> > >>
> > >> On Wed, Jun 26, 2024 at 5:30 AM Uwe Schindler <uw...@thetaphi.de>
> wrote:
> > >>> Hi,
> > >>>
> > >>> yes e.g., I have access to that machine and can issue a reboot. The
> two
> > >>> machines are VMs specifically owned by the Lucene PMC (not Solr as
> far
> > >>> as I remeber), but they were created before the split of projects.
> > >>>
> > >>> Some people have direct access, not sure how this is managed.
> Basically
> > >>> to get access you need to place a SSH key in id.apache.org -- and I
> > >>> think you need to be in the correct PMC.
> > >>>
> > >>> P.S.: I sometimes also run "apt update && apt dist-upgrade" to keep
> it
> > >>> uptodate (but not recently).
> > >>>
> > >>> Uwe
> > >>>
> > >>> Am 25.06.2024 um 20:20 schrieb Jason Gerlowski:
> > >>>> Hey all,
> > >>>>
> > >>>> Sending this email to discuss the ASF Jenkins' 'lucene-solr-1'
> worker
> > >>>> node, which both Lucene and Solr use to run builds.
> > >>>>
> > >>>> While investigating a recent issue with some Solr builds, I asked
> > >>>> INFRA to restart 'lucene-solr-1'. They were happy to oblige (and I'm
> > >>>> now unblocked), but in the process they mentioned that
> 'lucene-solr-1'
> > >>>> was a "project run VM" and that someone in the project should have
> the
> > >>>> requisite access and permissions. [1] [2]
> > >>>>
> > >>>> This was all a surprise to me, so I wanted to follow up here with a
> > >>>> few questions.
> > >>>>
> > >>>> 1. Is it true that our projects run or manage this VM in some way?
> > >>>> 2. If so, does anyone remember the context around how or why this
> came
> > >>>> about? (As opposed to using one of the "standard" Jenkins build
> > >>>> machines that INFRA provides...)
> > >>>> 3. Who all can access the box? How are credentials managed? (My
> > >>>> suspicion is that no one currently active on the Solr lists is able
> to
> > >>>> access the box, which seems worth remedying...)
> > >>>>
> > >>>> Best,
> > >>>>
> > >>>> Jason
> > >>>>
> > >>>> [1]
> https://lists.apache.org/thread/g0y0ohczdctv0v5fn8sqv4t0j4y6hp68
> > >>>> [2] https://the-asf.slack.com/archives/CBX4TSBQ8/p1719318685682309
> > >>>>
> > >>>>
> ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>
> > >>> --
> > >>> Uwe Schindler
> > >>> Achterdiek 19, D-28357 Bremen
> > >>> https://www.thetaphi.de
> > >>> eMail: uwe@thetaphi.de
> > >>>
> > >>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>
> > --
> > Uwe Schindler
> > Achterdiek 19, D-28357 Bremen
> > https://www.thetaphi.de
> > eMail: uwe@thetaphi.de
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: lucene-solr-1 Jenkins Agent Management
Posted by Jason Gerlowski <ge...@gmail.com>.
Thanks again Uwe!
On Wed, Jun 26, 2024 at 4:41 PM Uwe Schindler <uw...@thetaphi.de> wrote:
>
> Sorry,
>
> it's dead again. So fixing the stuck slave is up to ASF INFRA. Maybe its
> something like wrong Java version. Without any logfiles its impossible
> to guess.
>
> Uwe
>
> Am 26.06.2024 um 22:39 schrieb Uwe Schindler:
> > Hi,
> >
> > looks like killing the stuck slave process ("sudo pkill -9 -u
> > jenkins") helped lucene-solr-2 to recover.
> >
> > Uwe
> >
> > Am 26.06.2024 um 16:30 schrieb Jason Gerlowski:
> >> Hi Uwe
> >>
> >> Thanks for the context! A few follow-up questions for you (or anyone
> >> else that can answer):
> >>
> >> 1. What's the hostname for lucene-solr-1? Maybe my Jenkins knowledge
> >> is lacking, but I can't find the full hostname exposed anywhere in
> >> Jenkins, and I'd like to try SSH-ing in. (I'm hoping it might "just
> >> work" as I have a SSH key set up through id.apache.org and am on the
> >> Lucene PMC.)
> >> 2. AFAICT from its page in Jenkins
> >> (https://ci-builds.apache.org/computer/lucene%2Dsolr%2D2/),
> >> lucene-solr-2 has been "down" for some time. Does anyone know why
> >> this is?
> >> 3. Is there a particular reason why we have project-managed VMs,
> >> instead of using INFRA-managed nodes?
> >> 4. You mention that the VMs are only owned by the Lucene PMC. Is that
> >> mostly a historical accident (i.e. because the Solr PMC didn't
> >> technically exist at the time the VMs were created)? Or is there some
> >> conceptual reason the VMs should continue to be owned by Lucene PMC
> >> only?
> >>
> >> Best,
> >>
> >> Jason
> >>
> >> On Wed, Jun 26, 2024 at 5:30 AM Uwe Schindler <uw...@thetaphi.de> wrote:
> >>> Hi,
> >>>
> >>> yes e.g., I have access to that machine and can issue a reboot. The two
> >>> machines are VMs specifically owned by the Lucene PMC (not Solr as far
> >>> as I remeber), but they were created before the split of projects.
> >>>
> >>> Some people have direct access, not sure how this is managed. Basically
> >>> to get access you need to place a SSH key in id.apache.org -- and I
> >>> think you need to be in the correct PMC.
> >>>
> >>> P.S.: I sometimes also run "apt update && apt dist-upgrade" to keep it
> >>> uptodate (but not recently).
> >>>
> >>> Uwe
> >>>
> >>> Am 25.06.2024 um 20:20 schrieb Jason Gerlowski:
> >>>> Hey all,
> >>>>
> >>>> Sending this email to discuss the ASF Jenkins' 'lucene-solr-1' worker
> >>>> node, which both Lucene and Solr use to run builds.
> >>>>
> >>>> While investigating a recent issue with some Solr builds, I asked
> >>>> INFRA to restart 'lucene-solr-1'. They were happy to oblige (and I'm
> >>>> now unblocked), but in the process they mentioned that 'lucene-solr-1'
> >>>> was a "project run VM" and that someone in the project should have the
> >>>> requisite access and permissions. [1] [2]
> >>>>
> >>>> This was all a surprise to me, so I wanted to follow up here with a
> >>>> few questions.
> >>>>
> >>>> 1. Is it true that our projects run or manage this VM in some way?
> >>>> 2. If so, does anyone remember the context around how or why this came
> >>>> about? (As opposed to using one of the "standard" Jenkins build
> >>>> machines that INFRA provides...)
> >>>> 3. Who all can access the box? How are credentials managed? (My
> >>>> suspicion is that no one currently active on the Solr lists is able to
> >>>> access the box, which seems worth remedying...)
> >>>>
> >>>> Best,
> >>>>
> >>>> Jason
> >>>>
> >>>> [1] https://lists.apache.org/thread/g0y0ohczdctv0v5fn8sqv4t0j4y6hp68
> >>>> [2] https://the-asf.slack.com/archives/CBX4TSBQ8/p1719318685682309
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>
> >>> --
> >>> Uwe Schindler
> >>> Achterdiek 19, D-28357 Bremen
> >>> https://www.thetaphi.de
> >>> eMail: uwe@thetaphi.de
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >> For additional commands, e-mail: dev-help@lucene.apache.org
> >>
> --
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> https://www.thetaphi.de
> eMail: uwe@thetaphi.de
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: lucene-solr-1 Jenkins Agent Management
Posted by Uwe Schindler <uw...@thetaphi.de>.
Sorry,
it's dead again. So fixing the stuck slave is up to ASF INFRA. Maybe its
something like wrong Java version. Without any logfiles its impossible
to guess.
Uwe
Am 26.06.2024 um 22:39 schrieb Uwe Schindler:
> Hi,
>
> looks like killing the stuck slave process ("sudo pkill -9 -u
> jenkins") helped lucene-solr-2 to recover.
>
> Uwe
>
> Am 26.06.2024 um 16:30 schrieb Jason Gerlowski:
>> Hi Uwe
>>
>> Thanks for the context! A few follow-up questions for you (or anyone
>> else that can answer):
>>
>> 1. What's the hostname for lucene-solr-1? Maybe my Jenkins knowledge
>> is lacking, but I can't find the full hostname exposed anywhere in
>> Jenkins, and I'd like to try SSH-ing in. (I'm hoping it might "just
>> work" as I have a SSH key set up through id.apache.org and am on the
>> Lucene PMC.)
>> 2. AFAICT from its page in Jenkins
>> (https://ci-builds.apache.org/computer/lucene%2Dsolr%2D2/),
>> lucene-solr-2 has been "down" for some time. Does anyone know why
>> this is?
>> 3. Is there a particular reason why we have project-managed VMs,
>> instead of using INFRA-managed nodes?
>> 4. You mention that the VMs are only owned by the Lucene PMC. Is that
>> mostly a historical accident (i.e. because the Solr PMC didn't
>> technically exist at the time the VMs were created)? Or is there some
>> conceptual reason the VMs should continue to be owned by Lucene PMC
>> only?
>>
>> Best,
>>
>> Jason
>>
>> On Wed, Jun 26, 2024 at 5:30 AM Uwe Schindler <uw...@thetaphi.de> wrote:
>>> Hi,
>>>
>>> yes e.g., I have access to that machine and can issue a reboot. The two
>>> machines are VMs specifically owned by the Lucene PMC (not Solr as far
>>> as I remeber), but they were created before the split of projects.
>>>
>>> Some people have direct access, not sure how this is managed. Basically
>>> to get access you need to place a SSH key in id.apache.org -- and I
>>> think you need to be in the correct PMC.
>>>
>>> P.S.: I sometimes also run "apt update && apt dist-upgrade" to keep it
>>> uptodate (but not recently).
>>>
>>> Uwe
>>>
>>> Am 25.06.2024 um 20:20 schrieb Jason Gerlowski:
>>>> Hey all,
>>>>
>>>> Sending this email to discuss the ASF Jenkins' 'lucene-solr-1' worker
>>>> node, which both Lucene and Solr use to run builds.
>>>>
>>>> While investigating a recent issue with some Solr builds, I asked
>>>> INFRA to restart 'lucene-solr-1'. They were happy to oblige (and I'm
>>>> now unblocked), but in the process they mentioned that 'lucene-solr-1'
>>>> was a "project run VM" and that someone in the project should have the
>>>> requisite access and permissions. [1] [2]
>>>>
>>>> This was all a surprise to me, so I wanted to follow up here with a
>>>> few questions.
>>>>
>>>> 1. Is it true that our projects run or manage this VM in some way?
>>>> 2. If so, does anyone remember the context around how or why this came
>>>> about? (As opposed to using one of the "standard" Jenkins build
>>>> machines that INFRA provides...)
>>>> 3. Who all can access the box? How are credentials managed? (My
>>>> suspicion is that no one currently active on the Solr lists is able to
>>>> access the box, which seems worth remedying...)
>>>>
>>>> Best,
>>>>
>>>> Jason
>>>>
>>>> [1] https://lists.apache.org/thread/g0y0ohczdctv0v5fn8sqv4t0j4y6hp68
>>>> [2] https://the-asf.slack.com/archives/CBX4TSBQ8/p1719318685682309
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>
>>> --
>>> Uwe Schindler
>>> Achterdiek 19, D-28357 Bremen
>>> https://www.thetaphi.de
>>> eMail: uwe@thetaphi.de
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: uwe@thetaphi.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: lucene-solr-1 Jenkins Agent Management
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi,
looks like killing the stuck slave process ("sudo pkill -9 -u jenkins")
helped lucene-solr-2 to recover.
Uwe
Am 26.06.2024 um 16:30 schrieb Jason Gerlowski:
> Hi Uwe
>
> Thanks for the context! A few follow-up questions for you (or anyone
> else that can answer):
>
> 1. What's the hostname for lucene-solr-1? Maybe my Jenkins knowledge
> is lacking, but I can't find the full hostname exposed anywhere in
> Jenkins, and I'd like to try SSH-ing in. (I'm hoping it might "just
> work" as I have a SSH key set up through id.apache.org and am on the
> Lucene PMC.)
> 2. AFAICT from its page in Jenkins
> (https://ci-builds.apache.org/computer/lucene%2Dsolr%2D2/),
> lucene-solr-2 has been "down" for some time. Does anyone know why
> this is?
> 3. Is there a particular reason why we have project-managed VMs,
> instead of using INFRA-managed nodes?
> 4. You mention that the VMs are only owned by the Lucene PMC. Is that
> mostly a historical accident (i.e. because the Solr PMC didn't
> technically exist at the time the VMs were created)? Or is there some
> conceptual reason the VMs should continue to be owned by Lucene PMC
> only?
>
> Best,
>
> Jason
>
> On Wed, Jun 26, 2024 at 5:30 AM Uwe Schindler <uw...@thetaphi.de> wrote:
>> Hi,
>>
>> yes e.g., I have access to that machine and can issue a reboot. The two
>> machines are VMs specifically owned by the Lucene PMC (not Solr as far
>> as I remeber), but they were created before the split of projects.
>>
>> Some people have direct access, not sure how this is managed. Basically
>> to get access you need to place a SSH key in id.apache.org -- and I
>> think you need to be in the correct PMC.
>>
>> P.S.: I sometimes also run "apt update && apt dist-upgrade" to keep it
>> uptodate (but not recently).
>>
>> Uwe
>>
>> Am 25.06.2024 um 20:20 schrieb Jason Gerlowski:
>>> Hey all,
>>>
>>> Sending this email to discuss the ASF Jenkins' 'lucene-solr-1' worker
>>> node, which both Lucene and Solr use to run builds.
>>>
>>> While investigating a recent issue with some Solr builds, I asked
>>> INFRA to restart 'lucene-solr-1'. They were happy to oblige (and I'm
>>> now unblocked), but in the process they mentioned that 'lucene-solr-1'
>>> was a "project run VM" and that someone in the project should have the
>>> requisite access and permissions. [1] [2]
>>>
>>> This was all a surprise to me, so I wanted to follow up here with a
>>> few questions.
>>>
>>> 1. Is it true that our projects run or manage this VM in some way?
>>> 2. If so, does anyone remember the context around how or why this came
>>> about? (As opposed to using one of the "standard" Jenkins build
>>> machines that INFRA provides...)
>>> 3. Who all can access the box? How are credentials managed? (My
>>> suspicion is that no one currently active on the Solr lists is able to
>>> access the box, which seems worth remedying...)
>>>
>>> Best,
>>>
>>> Jason
>>>
>>> [1] https://lists.apache.org/thread/g0y0ohczdctv0v5fn8sqv4t0j4y6hp68
>>> [2] https://the-asf.slack.com/archives/CBX4TSBQ8/p1719318685682309
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>> --
>> Uwe Schindler
>> Achterdiek 19, D-28357 Bremen
>> https://www.thetaphi.de
>> eMail: uwe@thetaphi.de
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: uwe@thetaphi.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: lucene-solr-1 Jenkins Agent Management
Posted by Jason Gerlowski <ge...@gmail.com>.
Hi Uwe
Thanks for the context! A few follow-up questions for you (or anyone
else that can answer):
1. What's the hostname for lucene-solr-1? Maybe my Jenkins knowledge
is lacking, but I can't find the full hostname exposed anywhere in
Jenkins, and I'd like to try SSH-ing in. (I'm hoping it might "just
work" as I have a SSH key set up through id.apache.org and am on the
Lucene PMC.)
2. AFAICT from its page in Jenkins
(https://ci-builds.apache.org/computer/lucene%2Dsolr%2D2/),
lucene-solr-2 has been "down" for some time. Does anyone know why
this is?
3. Is there a particular reason why we have project-managed VMs,
instead of using INFRA-managed nodes?
4. You mention that the VMs are only owned by the Lucene PMC. Is that
mostly a historical accident (i.e. because the Solr PMC didn't
technically exist at the time the VMs were created)? Or is there some
conceptual reason the VMs should continue to be owned by Lucene PMC
only?
Best,
Jason
On Wed, Jun 26, 2024 at 5:30 AM Uwe Schindler <uw...@thetaphi.de> wrote:
>
> Hi,
>
> yes e.g., I have access to that machine and can issue a reboot. The two
> machines are VMs specifically owned by the Lucene PMC (not Solr as far
> as I remeber), but they were created before the split of projects.
>
> Some people have direct access, not sure how this is managed. Basically
> to get access you need to place a SSH key in id.apache.org -- and I
> think you need to be in the correct PMC.
>
> P.S.: I sometimes also run "apt update && apt dist-upgrade" to keep it
> uptodate (but not recently).
>
> Uwe
>
> Am 25.06.2024 um 20:20 schrieb Jason Gerlowski:
> > Hey all,
> >
> > Sending this email to discuss the ASF Jenkins' 'lucene-solr-1' worker
> > node, which both Lucene and Solr use to run builds.
> >
> > While investigating a recent issue with some Solr builds, I asked
> > INFRA to restart 'lucene-solr-1'. They were happy to oblige (and I'm
> > now unblocked), but in the process they mentioned that 'lucene-solr-1'
> > was a "project run VM" and that someone in the project should have the
> > requisite access and permissions. [1] [2]
> >
> > This was all a surprise to me, so I wanted to follow up here with a
> > few questions.
> >
> > 1. Is it true that our projects run or manage this VM in some way?
> > 2. If so, does anyone remember the context around how or why this came
> > about? (As opposed to using one of the "standard" Jenkins build
> > machines that INFRA provides...)
> > 3. Who all can access the box? How are credentials managed? (My
> > suspicion is that no one currently active on the Solr lists is able to
> > access the box, which seems worth remedying...)
> >
> > Best,
> >
> > Jason
> >
> > [1] https://lists.apache.org/thread/g0y0ohczdctv0v5fn8sqv4t0j4y6hp68
> > [2] https://the-asf.slack.com/archives/CBX4TSBQ8/p1719318685682309
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
> --
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> https://www.thetaphi.de
> eMail: uwe@thetaphi.de
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: lucene-solr-1 Jenkins Agent Management
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi,
yes e.g., I have access to that machine and can issue a reboot. The two
machines are VMs specifically owned by the Lucene PMC (not Solr as far
as I remeber), but they were created before the split of projects.
Some people have direct access, not sure how this is managed. Basically
to get access you need to place a SSH key in id.apache.org -- and I
think you need to be in the correct PMC.
P.S.: I sometimes also run "apt update && apt dist-upgrade" to keep it
uptodate (but not recently).
Uwe
Am 25.06.2024 um 20:20 schrieb Jason Gerlowski:
> Hey all,
>
> Sending this email to discuss the ASF Jenkins' 'lucene-solr-1' worker
> node, which both Lucene and Solr use to run builds.
>
> While investigating a recent issue with some Solr builds, I asked
> INFRA to restart 'lucene-solr-1'. They were happy to oblige (and I'm
> now unblocked), but in the process they mentioned that 'lucene-solr-1'
> was a "project run VM" and that someone in the project should have the
> requisite access and permissions. [1] [2]
>
> This was all a surprise to me, so I wanted to follow up here with a
> few questions.
>
> 1. Is it true that our projects run or manage this VM in some way?
> 2. If so, does anyone remember the context around how or why this came
> about? (As opposed to using one of the "standard" Jenkins build
> machines that INFRA provides...)
> 3. Who all can access the box? How are credentials managed? (My
> suspicion is that no one currently active on the Solr lists is able to
> access the box, which seems worth remedying...)
>
> Best,
>
> Jason
>
> [1] https://lists.apache.org/thread/g0y0ohczdctv0v5fn8sqv4t0j4y6hp68
> [2] https://the-asf.slack.com/archives/CBX4TSBQ8/p1719318685682309
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: uwe@thetaphi.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org