Slaves have wrong placement

[Loïc Minier]

Hi,

android-build.linaro.org jenkins slaves are started with the wrong placement: us-east-1a instead of us-east-1b.

We try to keep everything in us-east-1b to:
a) find our childs
b) save some money with reserved instances

android-build.l.o needs to be fixed to use us-east-1b.

Thanks!

[Deepti B. Kalakeri (deeptik)]

The problem can be fixed with jenkins ec2 plugin version 1.15 as it seems to have the facility to specify the Zone in which the slaves needs be started in .
Currently, we have ec2 1.14 plugin which means we need to upgrade it to 1.15 to make use of the feature.
I did some investigation and stumbled on the bug https://bugs.launchpad.net/linaro-android-infrastructure/+bug/1003831 which was raised to test/verify the ec2 plugin 1.16 version.
Since the bug is in progress I guess there is some effort still going on. I would wait for Paul before I started further on this bug to understand, what further needs to be done on the part of bug 1003831 so that we can deploy it on production system.

[Paul Sokolovsky (pfalcon)]

Well, my initial thinking when Loic raised this issue was "hey, I don't really know to specify instance zone/subregion in Jenkins". Well, I now see why bug 1003831 got attention. My idea was to re-raise this issue when I'll be on maint. team (next months). But as we now have good usecase for upgrade, let's do it sooner if possible. It will require updating build scripts, and may lead to wave of build breakage (well, we just had one with switch to new EULA handling system).

My initial changes for upgrade can be seen on instance i-1f150379 (may be used as reference, but apparently need to be redone to be sure).

[Deepti B. Kalakeri (deeptik)]

could you please elaborate on what kind of script changes needs to be done?
Do you have an estimate on the time we would need to accomplish everything ?

[Deepti B. Kalakeri (deeptik)]

As discussed on IRC between Paul and me, Paul would be picking up upgrading the a-b* to 1.16 jenkins version during his maintenance cycle as we need sometime to test the things properly before we upgrade the jenkins on a-b* or ci* otherwise.
Since there is only few days in maintenance left, the existing maintenance team can probably help with the initial testing so that next maintenance group can start working on upgrading the jenkins on a-b*.

[Deepti B. Kalakeri (deeptik)]

Un assigning myself to be picked up by this months maintenance team.

[Paul Sokolovsky (pfalcon)]

With ec2 plugin upgrade on a-b, I'm proceeding with configuring proper avail. zones.

[Paul Sokolovsky (pfalcon)]

Request for tagging extracted to lp:1067438 - it would have different priority.

[Paul Sokolovsky (pfalcon)]

Otherwise, a-b slaves now have proper placement. ci.linaro.org pending on lp:1003831