2020-02-13
§
|
21:35 |
<bd808> |
Deleted tools-sgewebgrid-lighttpd-092{1,2,3,4,5,6,7,8} & tools-sgewebgrid-generic-090{3,4} (T244791) |
[tools] |
21:33 |
<bd808> |
Removed tools-sgewebgrid-lighttpd-092{1,2,3,4,5,6,7,8} & tools-sgewebgrid-generic-090{3,4} from grid engine config (T244791) |
[tools] |
17:43 |
<andrewbogott> |
migrating b24e29d7-a468-4882-9652-9863c8acfb88 to cloudvirt1022 |
[tools] |
2020-01-30
§
|
21:04 |
<andrewbogott> |
also apt-get install python3-novaclient on tools-prometheus-03 and tools-prometheus-04 to suppress cronspam. Possible real fix for this is https://gerrit.wikimedia.org/r/#/c/operations/puppet/+/569084/ |
[tools] |
20:39 |
<andrewbogott> |
apt-get install python3-keystoneclient on tools-prometheus-03 and tools-prometheus-04 to suppress cronspam. Possible real fix for this is https://gerrit.wikimedia.org/r/#/c/operations/puppet/+/569084/ |
[tools] |
16:27 |
<arturo> |
create VM tools-prometheus-04 as cold standby of tools-prometheus-03 (T238096) |
[tools] |
16:25 |
<arturo> |
point tools-prometheus.wmflabs.org proxy to tools-prometheus-03 (T238096) |
[tools] |
13:42 |
<arturo> |
disable puppet in prometheus servers while syncing metric data (T238096) |
[tools] |
13:14 |
<arturo> |
drop floating IP 185.15.56.60 and FQDN `prometheus.tools.wmcloud.org` because this is not how the prometheus setup is right now. Use a web proxy instead `tools-prometheus-new.wmflabs.org` (T238096) |
[tools] |
13:09 |
<arturo> |
created FQDN `prometheus.tools.wmcloud.org` pointing to IPv4 185.15.56.60 (tools-prometheus-03) to test T238096 |
[tools] |
12:59 |
<arturo> |
associated floating IPv4 185.15.56.60 to tools-prometheus-03 (T238096) |
[tools] |
12:57 |
<arturo> |
created domain `tools.wmcloud.org` in the tools project after some back and forth with designated, permissions and the database. I plan to use this domain to test the new Debian Buster-based prometheus setup (T238096) |
[tools] |
10:20 |
<arturo> |
create new VM instance tools-prometheus-03 (T238096) |
[tools] |