Nice! I can't think of anything. I guess we just let it burn? I can't see any downside to just letting it go - it's just one more CI.
D. On Tue, Apr 22, 2025 at 7:30 PM Christos Malliaridis <c.malliari...@gmail.com> wrote: > > Infra provided us with two new nodes – lucene-solr-3 and lucene-solr-4 – to > replace the old ones. They come with upgraded hardware: > >> 16GB -> 32GB RAM >> 4CPU -> 16CPU >> 256/350GB -> 500GB disk > > > Once we are ready to turn off the old nodes, I'll respond to the Jira issue. > > What steps are still remaining before we can turn off the old nodes? > > Best, > Christos > > On Mon, Apr 7, 2025 at 8:09 PM Christos Malliaridis <c.malliari...@gmail.com> > wrote: >> >> I've requested an upgrade here: >> https://issues.apache.org/jira/browse/INFRA-26732 >> >> I hope I didn't forget anything. :) >> >> On Wed, Apr 2, 2025 at 10:19 PM Uwe Schindler <u...@thetaphi.de> wrote: >>> >>> Can you make sure that the same people get sudo/root acces slike before? >>> It would also be ideal to maybe ask them to preserve the jenkins >>> directory. I cleaned them up a bit already. >>> >>> If we get a new machine, could you ask them for more power and memory? >>> The current machines are very slow, looks like overprovisioned VMware! >>> >>> Am 02.04.2025 um 21:17 schrieb Uwe Schindler: >>> > Hi, >>> > >>> > go ahead. I preserved some config files. Actually the Gradle builds >>> > are easier to maintain as Ant, so basically it is just 2 files. >>> > >>> > Uwe >>> > >>> > Am 02.04.2025 um 17:21 schrieb Uwe Schindler: >>> >> Oh sorry, will do! I ping you. >>> >> >>> >> Uwe >>> >> >>> >> Am 02.04.2025 um 17:02 schrieb Christos Malliaridis: >>> >>> @Uwe Did you have the time to run a backup of the home directory? I >>> >>> would >>> >>> proceed and open an infra ticket if we are ready, I just need to >>> >>> know what "all >>> >>> packages we >>> >>> need for Jenkins Slaves" includes, as I am not sure how to look this >>> >>> up to >>> >>> include it in the ticket. >>> >>> >>> >>> Christos >>> >>> >>> >>> Hi, >>> >>> >>> >>> >>> >>>> I tried the do-release-upgrade on the older 18.04 machine. >>> >>>> Unfortunately >>> >>>> it does not work, as there are too many PPA repositories in the config >>> >>>> (nodejs,....) and those lead to package conflicts so >>> >>>> do-release-upgrade >>> >>>> bails out. >>> >>> >>> >>>> I could uninstall all those PPAs with "ppa-purge", but I don't know >>> >>>> how >>> >>>> to get puppet to reinstallthem after upgrade. >>> >>> >>> >>>> So it looks like we need to do the "rebuild node" with fresh OS >>> >>>> provided >>> >>>> by ASF. That's the problem of nailed down instances with horrible >>> >>>> puppet >>> >>>> (sorry, but puppet is the worst tool that I try to avoid at all of my >>> >>>> customers, it always causes issues administering machines for Solr >>> >>>> installations!). >>> >>> >>> >>>> I can do the jenkins home directory backup tomorrow and then we can >>> >>>> ask >>> >>> them to reinstall newer OS. We just need to make sure to tell them that >>> >>>> they should use a puppet configuration that contains all packages we >>> >>> need for Jenkins Slaves. >>> >>> >>> >>> >>> >>>> Uwe >>> >> >>> -- >>> Uwe Schindler >>> Achterdiek 19, D-28357 Bremen >>> https://www.thetaphi.de >>> eMail: u...@thetaphi.de >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org >>> For additional commands, e-mail: dev-h...@solr.apache.org >>> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
