infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-9096) Replace lucene.zones.apache.org by a similar Ubuntu-based VM
Date Wed, 18 Mar 2015 16:23:38 GMT

    [ https://issues.apache.org/jira/browse/INFRA-9096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14367404#comment-14367404
] 

Uwe Schindler commented on INFRA-9096:
--------------------------------------

Hi Chris,
thank you very much! In fact the machine currently runs as a Jenkins slave for Lucene Jobs
as a slave to ASF's Jenkins, but with a "customized" Jenkins home. Basically we currently
log in to the lucene.zones.apache.org machine with our private account that has sudo privileges
and then change to user "jenkins" and do setup work like installing new (preview) JDKs local
to the jenkins account to be fetched by the next Jenkins run. I hope we can do the same on
this new Lucene machine. I would take care of setting up the Jenkins infrastructure together
with the Jenkins admins at ASF - as usual :-)

For running our Jobs in general: the more CPU cores the better and some amount of RUM (but
not too much, several GiB is enough). We sometimes have so called nightly tests with so called
"monsters" that use several Gigabytes of Java Heap. As I said in my previous mail: Maybe something
similar to current lucene.zones. So, what could you spend? :-)

Software is quite simple: install the default openjdk7 from Ubuntu for booting up Jenkins,
but we also need SVN in the same version as Jenkins Master's configuration. The reason for
this is: Our build scripts run sometimes the native "svn" command to do some checks, so the
Jenkins Checkout format must be of the same version as the local SVN (unfortunately the checkout
format is given by the master configuration on ASF Jenkins, the local svn version is unrelated).
On FreeBSD we had a problem with that, so we symlinked the system SVN to a "svnkit" hack (a
java program similar to svn). We also need python 3.3+ (and python 2.7) and PERL. The Java
JDK versions for actually running the builds will be untarred by ourselves into ~jenkins/tools.

Would it be possible to get sudo authentication like on the previous machine, so we can do
the apt-get's on our side? For setting up the users, maybe copy the accounts from the current
machine together with their ssh public keys. All current accounts on that machine have sudo
rights.

If you give me a time, we can discuss on the INFRA chat. What's your timezone?

> Replace lucene.zones.apache.org by a similar Ubuntu-based VM
> ------------------------------------------------------------
>
>                 Key: INFRA-9096
>                 URL: https://issues.apache.org/jira/browse/INFRA-9096
>             Project: Infrastructure
>          Issue Type: Task
>          Components: VMWare, Zones/Jails
>            Reporter: Uwe Schindler
>            Assignee: Chris Lambertus
>
> We still run our Jenkins slave on the lucene.zones.apache.org jail (so we don't hurt
the other projects with our veeeeery extensive testing).
> Unfortunately, Lucene trunk changed to Java 8 - and Java 8 is broken on FreeBSD (tests
of Apache Solr crush the VM in the networking code - cause unknown). So we can currently only
run our stable tests for the Lucene/Solr 5.x branch and we build the artifacts with Java 8
on this machine (but no tests). We received the message from [~ke4qqq] that Sigyn will be
shut down in approx 90 days. I am not 100% sure if lucene.zones runs on this host, but a change
to Ubuntu (14.04 LTS) would be very helpful in any case, so we can run our extensive tests
in a separate machine.
> We want to migrate the current FreeBSD Jail to an Ubuntu virtual machine with similar
capacity. We need some additional data files on the Jenkins slave to run our special extensive
tests with lots of data and we would also like to maintain our own list of JDK versions, so
a separate Jenkins Slave with Root access (as currently) would be fine.
> We would take care about installing all additional software required for the Lucene build,
INFRA would just need to setup the private keys for the Jenkins master to log in (more or
less only change ip address of slave node "lucene", so we can keep all our configured jobs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message