infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (INFRA-15453) Request for configuration of Jenkins Slaves
Date Tue, 07 Nov 2017 08:00:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-15453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gavin reassigned INFRA-15453:
-----------------------------

    Assignee: Gavin

> Request for configuration of Jenkins Slaves
> -------------------------------------------
>
>                 Key: INFRA-15453
>                 URL: https://issues.apache.org/jira/browse/INFRA-15453
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: Jenkins
>            Reporter: Chris Olivier
>            Assignee: Gavin
>              Labels: CI
>
> Hello Infra,
> In order to reduce load on your side, we're proposing a change regarding the communication
between Master and Slave. After discussion on our slack-channel (https://the-asf.slackarchive.io/mxnet-builds/page-10)
we came to the conclusion that the usage of JNLP Web Agents might be a good idea. This way,
a slave only has to be created once and the assigned secret can be reused. In case we have
to stop, restart or start a slave, we can just use a secret which is not in use in order to
connect the new slave to the master without requiring any interaction from Infra.
> Therefor we'd like to request 15 slaves tagged as mxnet-linux and 15 slaves as mxnet-windows.
After sending us the generated secrets and the active JNLP-Port, we'll be able to manage slaves
completely on our own.
> If there's a need for whitelisting IPs to access the JNLP-Port, we'd be happy to supply
you with a number of Elastic IPs which we will be using in future.
> Thank you,
> Chris Olivier
> Commiter, Apache MXNet (incubating)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message