351-400 of 423 results (31ms)
2020-06-11 §
11:11 <arturo> deployed nginx-ingress for some early testing (not definitive) with code https://github.com/crookedstorm/paws/commit/bee62b3fd57f9804aa27e7b8b41fde50bd93df94 (T195217) [paws]
10:15 <arturo> added role (just a label) for ingress nodes: `kubectl label node paws-k8s-ingress-1 kubernetes.io/role=ingress` (T195217) [paws]
2020-06-04 §
14:16 <arturo> added node taints to ingress nodes: `kubectl taint nodes paws-k8s-ingress-1 ingress=true:NoSchedule` (T195217) [paws]
12:18 <arturo> bootstrapped paws-k8s-ingress nodes, added them to the k8s cluster (T195217) [paws]
12:04 <arturo> created `paws-k8s-ingress` puppet prefix and add the `role::wmcs::paws::k8s::worker` role (T195217) [paws]
12:02 <arturo> created 2 medium VM instances: paws-k8s-ingress-1 and paws-k8s-ingress-2 with haproxy anti-affinity (T195217) [paws]
2020-05-26 §
22:34 <bstorm_> restored the deployment for maintain-kubeusers so anyone added to the paws.admin group will have admin on the cluster now that the bug is fixed T211096 T246059 [paws]
22:05 <bstorm_> temporarily deleted the deployment for maintain-kubeusers pending patch to fix context creation for new admin accounts T211096 T246059 [paws]
22:04 <bstorm_> created paws-focused PodSecurityPolicies and the prod namespace in the new cluster T211096 [paws]
22:03 <bstorm_> created paws.admin group and kubernetes admin accounts on the new k8s cluster T211096 T246059 [paws]
18:29 <bstorm_> bootstrapped the new control plane nodes T211096 [paws]
15:27 <bstorm_> updated profile::wmcs::kubeadm::kubernetes_version to 1.16.10 for cluster init T211096 [paws]
2020-05-21 §
23:04 <bstorm_> added profile::wmcs::kubeadm::k8s::encryption_key and profile::wmcs::kubeadm::k8s::node_token to labs/private T211096 [paws]
14:53 <bstorm_> adding the hiera values to horizon for bootstrapping k8s T211096 [paws]
14:39 <arturo> point record `k8s.svc.paws.eqiad1.wikimedia.cloud` to `172.16.1.186` (which is paws-k8s-control-1, for the initial bootstrap) (T211096) [paws]
12:48 <arturo> created record `k8s.svc.paws.eqiad1.wikimedia.cloud` pointing to `172.16.0.191` (which is paws-k8s-haproxy-1) (T211096) [paws]
12:34 <arturo> created and transferred DNS zone `svc.paws.eqiad1.wikimedia.cloud` (T211096) [paws]
2020-05-20 §
22:35 <bstorm_> created paws-k8s-worker-1/2/3/4 T211096 [paws]
22:12 <bstorm_> created paws-k8s-haproxy-1/2 with antiaffinity group T211096 [paws]
21:36 <bstorm_> created paws-k8s-control-1/2/3 with appropriate sec group and server group T211096 [paws]
18:59 <bstorm_> created anti-affinity group "controlplane" T211096 [paws]
16:38 <bstorm_> deleting the old shut-down VMs from the last effort to rebuild paws T211096 [paws]
16:36 <bstorm_> cleaned up the old DNS entries for the external LBs that have been off for a year [paws]
2020-03-20 §
14:03 <jeh> upgrade paws-puppetmaster-01 to v5 T241719 [paws]
2020-02-14 §
21:31 <andrewbogott> restarting paws-puppetmaster-01 so its clients can connect [paws]
2020-01-09 §
18:06 <bstorm_> rebooting tools-paws-master-01 T242353 [paws]
14:28 <chicocvenancio> shutdown unused instances [paws]
2019-12-13 §
00:27 <bstorm_> rebooting the paws master since it is in a bad state after the openstack maintenance as well. [paws]
2019-11-01 §
21:15 <Krenair> Updated paws-apiserver.wmflabs.org A record list to remove 172.16.2.151 which is not allocated to any instance. The other two A records point to valid instances in the paws project. [paws]
2019-10-23 §
09:03 <arturo> paws-master-01/03 and a couple of other servers are down because hypervisor is rebooting [paws]
2019-10-14 §
22:32 <bd808> Removed project member "Afrodric". Looks like someone added accidentally when trying to make aborrero as project member [paws]
22:31 <bd808> Added Krenair as project member [paws]
2019-05-18 §
11:13 <chicocvenancio> point paws-proxy-02 to tools-paws-worker-1006 on paws-deploy-hook hostname (T218380) [paws]
2019-04-26 §
15:27 <chicocvenancio> paws-proxy-02 redirecting main page to https://www.mediawiki.org/wiki/PAWS T221886 [paws]
2019-04-16 §
17:15 <chicocvenancio> move paws-proxy-02 reload nginx [paws]
17:07 <chicocvenancio> move paws-proxy-02 to point to tools-paws-worker-1006 for upcoming master move [paws]
2019-03-27 §
23:46 <chicocvenancio> moving paws host in `paws-proxy-02` back to `tools-paws-master-01` T219460 [paws]
22:10 <chicocvenancio> moving paws host in `paws-proxy-02` to `tools-paws-worker-1005` T219460 [paws]
2019-03-25 §
14:12 <gtirloni> created `paws.wmflabs.org` subdomain under `paws` project (T211096) [paws]
14:07 <gtirloni> created `paws.wmflabs.org` subdomain under `paws` project T211096 [paws]
13:54 <gtirloni> created `paws.wmflabs.org` subdomain under `paws` project (T211096) [paws]
2019-03-15 §
02:25 <gtirloni> activated TLS termination using Let's Encrypt on paws-proxy-02 [paws]
02:25 <gtirloni> removed webproxies and created new A records pointing directly to paws-proxy-02 [paws]
2019-02-21 §
09:22 <gtirloni> upgraded and rebooted paws-proxy-02 [paws]
2019-02-20 §
15:00 <andrewbogott> deleting the long-shut-down paws-proxy-01 [paws]
2019-02-15 §
01:28 <bd808> Re-enabled PAWS vhost on paws-proxy-02 [paws]
2019-02-14 §
22:25 <gtirloni> downtimed PAWS in Icinga [paws]
22:16 <gtirloni> Activated maintenance page on paws-proxy-02 nginx config [paws]
2019-02-13 §
08:32 <arturo> switch paws-proxy-02 puppetmaster to labs-puppetmaster.wikimedia.org [paws]
2019-01-24 §
19:20 <andrewbogott> shutting down paws-proxy-01 [paws]