Migrate m4executor CI nodes to bigram instances
Closed, ResolvedPublic

Description

dduvall created this task.Sep 25 2018, 12:00 AM
dduvall triaged this task as Normal priority.
dduvall moved this task from Backlog to In-progress on the Release-Engineering-Team (Kanban) board.

Mentioned in SAL (#wikimedia-releng) [2018-09-25T17:09:29Z] <marxarelli> deleting integration-slave-docker-1030/1031 instances (T205362)

Mentioned in SAL (#wikimedia-releng) [2018-09-25T17:12:22Z] <marxarelli> taking integration-slave-docker-1007/1008 offline for replacement (T205362)

Mentioned in SAL (#wikimedia-releng) [2018-09-25T17:24:09Z] <marxarelli> deleting instances integration-slave-docker-1007/1008 (T205362)

Mentioned in SAL (#wikimedia-releng) [2018-09-25T17:25:29Z] <marxarelli> launching integration-slave-docker-1040 bigram instance (T205362)

Mentioned in SAL (#wikimedia-releng) [2018-09-25T17:38:14Z] <marxarelli> launching integration-slave-docker-1041 bigram instance (T205362)

Mentioned in SAL (#wikimedia-releng) [2018-09-25T17:42:28Z] <marxarelli> configuring new jenkins node integration-slave-docker-1040 with 7 executors (T205362)

Mentioned in SAL (#wikimedia-releng) [2018-09-25T18:00:16Z] <marxarelli> configuring new integration-slave-docker-1041 jenkins node with 7 executors (T205362)

Mentioned in SAL (#wikimedia-releng) [2018-09-25T18:16:16Z] <marxarelli> reconfiguring bigram jenkins nodes to use 6 executors. 7 were configured by mistake (T205362)

Mentioned in SAL (#wikimedia-releng) [2018-09-25T22:15:17Z] <marxarelli> taking remaining m1.medium m4executor jenkins nodes offline (T205362)

Mentioned in SAL (#wikimedia-releng) [2018-09-25T22:33:16Z] <marxarelli> deleting remaining m1.medium instances used as m4executors (T205362)

dduvall closed this task as Resolved.Sep 25 2018, 11:04 PM

All Jenkins m4executor nodes that were backed by m1.medium instances have been replaced.

Thank you Dan to have dig into all those metrics.