|
2019-05-14
§
|
| 17:12 |
<arturo> |
T223148 repool tools-sgeexec-0920 |
[tools] |
| 16:37 |
<arturo> |
T223148 depool tools-sgeexec-0920 and reallocate to cloudvirt1003 |
[tools] |
| 16:36 |
<arturo> |
T223148 repool tools-sgeexec-0911 |
[tools] |
| 15:56 |
<arturo> |
T223148 depool tools-sgeexec-0911 and reallocate to cloudvirt1003 |
[tools] |
| 15:52 |
<arturo> |
T223148 repool tools-sgeexec-0909 |
[tools] |
| 15:24 |
<arturo> |
T223148 depool tools-sgeexec-0909 and reallocate to cloudvirt1002 |
[tools] |
| 15:24 |
<arturo> |
T223148 last SAL entry is bogus, please ignore (depool tools-worker-1009) |
[tools] |
| 15:23 |
<arturo> |
T223148 depool tools-worker-1009 |
[tools] |
| 15:13 |
<arturo> |
T223148 repool tools-worker-1023 |
[tools] |
| 13:16 |
<arturo> |
T223148 repool tools-sgeexec-0942 |
[tools] |
| 13:03 |
<arturo> |
T223148 repool tools-sgewebgrid-generic-0904 |
[tools] |
| 12:58 |
<arturo> |
T223148 reallocating tools-worker-1023 to cloudvirt1001 |
[tools] |
| 12:56 |
<arturo> |
T223148 depool tools-worker-1023 |
[tools] |
| 12:52 |
<arturo> |
T223148 reallocating tools-sgeexec-0942 to cloudvirt1001 |
[tools] |
| 12:50 |
<arturo> |
T223148 depool tools-sgeexec-0942 |
[tools] |
| 12:49 |
<arturo> |
T223148 reallocating tools-sgewebgrid-generic-0904 to cloudvirt1001 |
[tools] |
| 12:43 |
<arturo> |
T223148 depool tools-sgewebgrid-generic-0904 |
[tools] |
|
2019-05-07
§
|
| 14:38 |
<arturo> |
T222718 uncordon tools-worker-1019, I couldn't find a reason for it to be cordoned |
[tools] |
| 14:31 |
<arturo> |
T222718 reboot tools-worker-1009 and 1022 after being drained |
[tools] |
| 14:28 |
<arturo> |
k8s drain tools-worker-1009 and 1022 |
[tools] |
| 11:46 |
<arturo> |
T219362 enable puppet in tools-redis servers and use the new puppet role |
[tools] |
| 11:33 |
<arturo> |
T219362 disable puppet in tools-reds servers for puppet code cleanup |
[tools] |
| 11:12 |
<arturo> |
T219362 drop the `tools-services` puppet prefix (we are actually using `tools-sgeservices`) |
[tools] |
| 11:10 |
<arturo> |
T219362 enable puppet in tools-static servers and use new puppet role |
[tools] |
| 11:01 |
<arturo> |
T219362 disable puppet in tools-static servers for puppet code cleanup |
[tools] |
| 10:16 |
<arturo> |
T219362 drop the `tools-webgrid-lighttpd` puppet prefix |
[tools] |
| 10:14 |
<arturo> |
T219362 drop the `tools-webgrid-generic` puppet prefix |
[tools] |
| 10:06 |
<arturo> |
T219362 drop the `tools-exec-1` puppet prefix |
[tools] |
|
2019-05-03
§
|
| 09:43 |
<arturo> |
fixed puppet in tools-puppetdb-01 too |
[tools] |
| 09:39 |
<arturo> |
puppet should be now fine across toolforge (except tools-puppetdb-01 which is WIP I think) |
[tools] |
| 09:37 |
<arturo> |
fix puppet in tools-elastic-03, archived jessie repos, weird rsyslog-kafka package situation |
[tools] |
| 09:33 |
<arturo> |
fix puppet in tools-elastic-02, archived jessie repos, weird rsyslog-kafka package situation |
[tools] |
| 09:24 |
<arturo> |
fix puppet in tools-elastic-01, archived jessie repos, weird rsyslog-kafka package situation |
[tools] |
| 09:18 |
<arturo> |
solve a weird apt situation in tools-puppetmaster-01 regarding the rsyslog-kafka package (puppet agent was failing) |
[tools] |
| 09:16 |
<arturo> |
solve a weird apt situation in tools-worker-1028 regarding the rsyslog-kafka package |
[tools] |