From 6557040dc52296bfc033449f092cf4504e641bce Mon Sep 17 00:00:00 2001 From: Tim Stewart Date: Wed, 20 Jan 2021 11:47:30 -0800 Subject: [PATCH 01/12] started cleaning --- README.md | 14 +++++--------- {ansible => flock-archive/ansible}/hosts | 0 {ansible => flock-archive/ansible}/misc/htop.yml | 0 {ansible => flock-archive/ansible}/misc/hwe.yml | 0 {ansible => flock-archive/ansible}/misc/test.yml | 0 {ansible => flock-archive/ansible}/misc/test2.yml | 0 .../ansible}/playbooks/init.yml | 0 .../ansible}/playbooks/kube-deps.yml | 0 .../ansible}/playbooks/main.yml | 0 .../ansible}/playbooks/master.yml | 0 .../ansible}/playbooks/workers.yml | 0 calico.yml => flock-archive/calico.yml | 0 chicks.csv => flock-archive/chicks.csv | 0 get_macs.py => flock-archive/get_macs.py | 0 .../metallb-config.yml | 0 .../nfs-client-vals.yml | 0 16 files changed, 5 insertions(+), 9 deletions(-) rename {ansible => flock-archive/ansible}/hosts (100%) rename {ansible => flock-archive/ansible}/misc/htop.yml (100%) rename {ansible => flock-archive/ansible}/misc/hwe.yml (100%) rename {ansible => flock-archive/ansible}/misc/test.yml (100%) rename {ansible => flock-archive/ansible}/misc/test2.yml (100%) rename {ansible => flock-archive/ansible}/playbooks/init.yml (100%) rename {ansible => flock-archive/ansible}/playbooks/kube-deps.yml (100%) rename {ansible => flock-archive/ansible}/playbooks/main.yml (100%) rename {ansible => flock-archive/ansible}/playbooks/master.yml (100%) rename {ansible => flock-archive/ansible}/playbooks/workers.yml (100%) rename calico.yml => flock-archive/calico.yml (100%) rename chicks.csv => flock-archive/chicks.csv (100%) rename get_macs.py => flock-archive/get_macs.py (100%) rename metallb-config.yml => flock-archive/metallb-config.yml (100%) rename nfs-client-vals.yml => flock-archive/nfs-client-vals.yml (100%) diff --git a/README.md b/README.md index 07f0c6e..251b603 100644 --- a/README.md +++ b/README.md @@ -1,17 +1,17 @@ # Metal Cluster -This is our repo for everything involving our bare-metal Kubernetes cluster. At this moment, +This is our repo for everything related to the now-depreciated "flock" Kubernetes cluster. At this moment, it also contains documentation for setting up Kubernetes, JupyterHub, and BinderHub on Google Cloud. The folder [docs](./docs) contains all documentation related to these topics. -The root of this repository contains files relating to the set-up of the bare-metal cluster, +The folder [flock-archive](./flock-archive) contains files relating to the set-up of the flock cluster. ## Table of Contents This discusses the table of contents of [documentation](./docs) folder based on the following topics. ### Bare-Metal -1. [Bare Metal Cluster Setup](./docs/Bare-Metal/baremetal.md) has what you should read first about - the cluster. The file gives an overview of the cluster set-up, including networking, publishing services, - instructions on adding nodes, and useful resources. +1. [Bare Metal Cluster Setup](./docs/Bare-Metal/baremetal.md) has reading material on nearly every +aspect of the flock cluster. The file gives an overview of the cluster set-up, including networking, publishing services, +instructions on adding nodes, and useful resources. #### Concepts 1. [RAID.md](./docs/Bare-Metal/concepts/RAID.md) describes the purpose and different levels of RAID. @@ -36,8 +36,6 @@ setting up JupyterHub on a virtual machine. It contains solutions to the problem when installing JupyterHub through the [jupyterhub-deploy-teaching](https://github.com/mechmotum/jupyterhub-deploy-teaching) repository. We keep this as a reference for those who might encounter the same problems in the future. - - ### JupyterHub on GCloud This section teaches how to set-up and configure JupyterHub on Google Cloud. @@ -57,5 +55,3 @@ on a Kubernetes cluster on Google Cloud. We created a development [cluster of vms](./dev-env) using Vagrant that is nice for testing stuff without having it on the main cluster. This section contains files and instructions implementing the test cluster. - - diff --git a/ansible/hosts b/flock-archive/ansible/hosts similarity index 100% rename from ansible/hosts rename to flock-archive/ansible/hosts diff --git a/ansible/misc/htop.yml b/flock-archive/ansible/misc/htop.yml similarity index 100% rename from ansible/misc/htop.yml rename to flock-archive/ansible/misc/htop.yml diff --git a/ansible/misc/hwe.yml b/flock-archive/ansible/misc/hwe.yml similarity index 100% rename from ansible/misc/hwe.yml rename to flock-archive/ansible/misc/hwe.yml diff --git a/ansible/misc/test.yml b/flock-archive/ansible/misc/test.yml similarity index 100% rename from ansible/misc/test.yml rename to flock-archive/ansible/misc/test.yml diff --git a/ansible/misc/test2.yml b/flock-archive/ansible/misc/test2.yml similarity index 100% rename from ansible/misc/test2.yml rename to flock-archive/ansible/misc/test2.yml diff --git a/ansible/playbooks/init.yml b/flock-archive/ansible/playbooks/init.yml similarity index 100% rename from ansible/playbooks/init.yml rename to flock-archive/ansible/playbooks/init.yml diff --git a/ansible/playbooks/kube-deps.yml b/flock-archive/ansible/playbooks/kube-deps.yml similarity index 100% rename from ansible/playbooks/kube-deps.yml rename to flock-archive/ansible/playbooks/kube-deps.yml diff --git a/ansible/playbooks/main.yml b/flock-archive/ansible/playbooks/main.yml similarity index 100% rename from ansible/playbooks/main.yml rename to flock-archive/ansible/playbooks/main.yml diff --git a/ansible/playbooks/master.yml b/flock-archive/ansible/playbooks/master.yml similarity index 100% rename from ansible/playbooks/master.yml rename to flock-archive/ansible/playbooks/master.yml diff --git a/ansible/playbooks/workers.yml b/flock-archive/ansible/playbooks/workers.yml similarity index 100% rename from ansible/playbooks/workers.yml rename to flock-archive/ansible/playbooks/workers.yml diff --git a/calico.yml b/flock-archive/calico.yml similarity index 100% rename from calico.yml rename to flock-archive/calico.yml diff --git a/chicks.csv b/flock-archive/chicks.csv similarity index 100% rename from chicks.csv rename to flock-archive/chicks.csv diff --git a/get_macs.py b/flock-archive/get_macs.py similarity index 100% rename from get_macs.py rename to flock-archive/get_macs.py diff --git a/metallb-config.yml b/flock-archive/metallb-config.yml similarity index 100% rename from metallb-config.yml rename to flock-archive/metallb-config.yml diff --git a/nfs-client-vals.yml b/flock-archive/nfs-client-vals.yml similarity index 100% rename from nfs-client-vals.yml rename to flock-archive/nfs-client-vals.yml From 8f1b74aed263edc5dfd7549478858701d727af09 Mon Sep 17 00:00:00 2001 From: Tim Stewart Date: Sun, 24 Jan 2021 14:18:29 -0800 Subject: [PATCH 02/12] updated login.md --- docs/Bare-Metal/login.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/docs/Bare-Metal/login.md b/docs/Bare-Metal/login.md index 0be81e7..1e79242 100644 --- a/docs/Bare-Metal/login.md +++ b/docs/Bare-Metal/login.md @@ -1,10 +1,7 @@ # Login This JupyterHub serves LibreTexts instructors and their students, as well as UC Davis faculty, staff, and students. -## Request an account -If you are a LibreTexts or UC Davis student, please request an account by sending your -Google OAuth enabled email to . Your email address must have a Google Account -that can be used with Google OAuth, like `@gmail.com` or `@ucdavis.edu`. +If you are a UC Davis student, access to this JupyterHub is already granted. Just login with your school email. ## Getting started with Jupyter [Jupyter](https://jupyter.org/index.html) is an environment where you can From 1a5acbcb5dba07ba454e04c11558f676a1f67cfa Mon Sep 17 00:00:00 2001 From: Tim Stewart Date: Sun, 24 Jan 2021 14:42:48 -0800 Subject: [PATCH 03/12] updated troubleshooting readme --- docs/Bare-Metal/troubleshooting/README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/Bare-Metal/troubleshooting/README.md b/docs/Bare-Metal/troubleshooting/README.md index 73da878..bf33191 100644 --- a/docs/Bare-Metal/troubleshooting/README.md +++ b/docs/Bare-Metal/troubleshooting/README.md @@ -4,10 +4,10 @@ If the troubleshooting that you are doing for a particular problem is ineffectiv 1. You may be looking at symptoms unrelated to the problem. * Fixing this is a matter of becoming better aquainted with the system. The following are some resources that you may want to review: - 1. [Bare-Metal](https://github.com/LibreTexts/metalc/blob/docs/Troubleshooting-Summary/docs/Bare-Metal/baremetal.md) - 2. [BinderHub](https://github.com/LibreTexts/metalc/blob/docs/Troubleshooting-Summary/docs/Binder-on-GCloud/01-BinderHub.md) - 3. [Maintenance](https://github.com/LibreTexts/metalc/blob/docs/Troubleshooting-Summary/docs/maintenance-tasks.md) - 4. [Adding new packages to the Dockerfile](https://github.com/LibreTexts/default-env/tree/master/rich-default) + 1. Documentation in galaxy-control-repo + 2. [BinderHub](./docs/Binder-on-GCloud/01-BinderHub.md) + 3. [Maintenance](./docs/maintenance-tasks.md) + 4. [Adding new packages to the Dockerfile](https://github.com/LibreTexts/default-env/) 2. Not fully understanding how to change the system such the inputs, outputs, the environment, and etc. * This is similar to the previous example, make sure you have good knowledge of the system you are looking at. Visit any of the above links, and feel free check out any other documentation. The following may potentially be relevant: @@ -16,7 +16,7 @@ If the troubleshooting that you are doing for a particular problem is ineffectiv 3. [BinderHub FAQ](https://mybinder.readthedocs.io/en/latest/faq.html) 3. Assuming that the problem you are facing is the same as one you have previously dealt with given that the symptoms are the same. * If you are dealing with similar symptoms definitly look into how you have previously handled the issue, or how solutions have been documented - [here](https://github.com/LibreTexts/metalc/tree/docs/Troubleshooting-Summary/docs/Bare-Metal/troubleshooting). Howevever, if you have tried everything you + [here](./docs/Bare-Metal/troubleshooting/). Howevever, if you have tried everything you have done before, it might be worth trying something different. A good example of this kind of dilema is [this issue](https://github.com/LibreTexts/metalc/blob/master/docs/Bare-Metal/troubleshooting/KubeadmCert.md) we had. From b4f785f467bf54dd18a9cfeb62ef2e42df5542d8 Mon Sep 17 00:00:00 2001 From: Tim Stewart Date: Sun, 24 Jan 2021 14:55:57 -0800 Subject: [PATCH 04/12] fix broken links --- docs/Bare-Metal/troubleshooting/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/Bare-Metal/troubleshooting/README.md b/docs/Bare-Metal/troubleshooting/README.md index bf33191..b02d45b 100644 --- a/docs/Bare-Metal/troubleshooting/README.md +++ b/docs/Bare-Metal/troubleshooting/README.md @@ -5,8 +5,8 @@ If the troubleshooting that you are doing for a particular problem is ineffectiv 1. You may be looking at symptoms unrelated to the problem. * Fixing this is a matter of becoming better aquainted with the system. The following are some resources that you may want to review: 1. Documentation in galaxy-control-repo - 2. [BinderHub](./docs/Binder-on-GCloud/01-BinderHub.md) - 3. [Maintenance](./docs/maintenance-tasks.md) + 2. [BinderHub](/docs/Binder-on-GCloud/01-BinderHub.md) + 3. [Maintenance](/docs/maintenance-tasks.md) 4. [Adding new packages to the Dockerfile](https://github.com/LibreTexts/default-env/) 2. Not fully understanding how to change the system such the inputs, outputs, the environment, and etc. * This is similar to the previous example, make sure you have good knowledge of the system you are looking at. Visit any of the above links, and feel free @@ -16,7 +16,7 @@ If the troubleshooting that you are doing for a particular problem is ineffectiv 3. [BinderHub FAQ](https://mybinder.readthedocs.io/en/latest/faq.html) 3. Assuming that the problem you are facing is the same as one you have previously dealt with given that the symptoms are the same. * If you are dealing with similar symptoms definitly look into how you have previously handled the issue, or how solutions have been documented - [here](./docs/Bare-Metal/troubleshooting/). Howevever, if you have tried everything you + [here](/docs/Bare-Metal/troubleshooting/). Howevever, if you have tried everything you have done before, it might be worth trying something different. A good example of this kind of dilema is [this issue](https://github.com/LibreTexts/metalc/blob/master/docs/Bare-Metal/troubleshooting/KubeadmCert.md) we had. From 05438e05b8fb3fd1000caa1adfe357f4e0346a73 Mon Sep 17 00:00:00 2001 From: Tim Stewart Date: Tue, 26 Jan 2021 12:41:02 -0800 Subject: [PATCH 05/12] casual cleaning --- docs/.JupyterBareMetalWithLVM.md.swo | Bin 16384 -> 0 bytes docs/.JupyterBareMetalWithLVM.md.swp | Bin 16384 -> 0 bytes docs/maintenance-tasks.md | 54 ++++++++++++------ docs/updating-ubuntu-kubernetes.md | 19 +++++- .../Bare-Metal => flock-archive}/baremetal.md | 0 5 files changed, 51 insertions(+), 22 deletions(-) delete mode 100644 docs/.JupyterBareMetalWithLVM.md.swo delete mode 100644 docs/.JupyterBareMetalWithLVM.md.swp rename {docs/Bare-Metal => flock-archive}/baremetal.md (100%) diff --git a/docs/.JupyterBareMetalWithLVM.md.swo b/docs/.JupyterBareMetalWithLVM.md.swo deleted file mode 100644 index db25e2bd336287346ff53a76f0d8f4b4cc447198..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 16384 zcmeI2U2Ggz6~`w<{Qw%i${S5`ii=3B^{#i5h}1+CNt`B5y}`tZ^8jf*o}JyDdUj?t zA9f9*g%>1H3pBidT8Rg~3WyJhuTppcp7>}B^npHrprP;veQ1$d3W49bGvkfZfCDe3 z;;#IYF{}-NBlt-gD*CcRNlx47@eHzR4$v z<23V=O?o-bU1q?>z|Y*!Yjk2SZ5+#oYutL!P5icAJ{@HJ*@bp}(Ajh}+rcVe6}W5# z@~k_tZ|kYut)^M(V{g7eu6x6&%f8)qv$(xDC$0-(KT5FTh{n zDfm772!04ZfG@+B;Dhi1xE*eTHq64Ua18dqHh6xk<2(oF;7Rx${1%qsFV{NGv+xZ3 z27V3Shws4ya6in#t#AVf?11fX1^n^Vj`Ih23VsSdflt9F!G%S*9S*}Z?11gC4X%eL zUWGpJ7Pt|%!S(Pac;S_30O#OI_&GcVUx%;3SK(f`2Qo+@fIb|CY1j_i;QTd?^LKa@ z9)X|1H{l!b5%@5qkiZhSun0R~JDk6o`{5z@4h$iNo$yw8BU}gHy^22YIruDm20jgE z;iGUboPv`u2XBMj(1K^lmuKKEin1?66CWrX%%?6Dli}PA_*c{O8!%$fk+>^Wdy+>{5cMREB7nXV5#x}osb z85WG#Ra2|c=2GE^NLwbt;%AW_GN!1 z>&@?2S5PK~q9QJ$?!3F=BY`iepJgbL>NP);qbMzNstPu>vr*?r?!V|Vy3}RX*KuM7 zN>W)0-Dr6|a&BkEjXb|oSug{6Vc;#R`bPL}oUFP@M+2h4cRRooLX!)Qa{wp$$T^Hr zfL3?N9Hl8~KhDFBEYU5?T(6G}oIQTvWL-mn_%-qRZq)N7$cj8-o(t{DkyOro=&ZNlHspkJOArMFc!<3~@2=Ea zO@hoXCvM#B1gS=2I*!((EcvjMw7Q$8lsHFSqw$n9WWvml*Bvv~50OaMc<*t*A(=lU~3I;BQ?_9lz`5VJ2ztUSD>S-lF&Gwt{rcJ$v^``{1tne`QN$tV}ic zq49=c3Rk6<#QCr$W;?}d>G8ZD`d)@}D}kp$B+UG~G3Yc&563waN8O;8Cq+PJ%gHa8 z$xGXf+@8MoN=9E&o|F+rxzV~XX==LSj4p#wj_E>bERkN=o{8kdftl%M<=WV!-eR0p zHH%!@5U!CII>e|6Cp3U&UTMc|ndMvlwba_s*4)t6R0ZbTATfS+&HB_8Rfv_!YTu8< z)4bp+`EoKA&Yd)#s?=yt%d`=;X67QzT5-1F0*jl}s7BHqZcSAvcov%|6fhHG_E;oM?%@|06VeMTQtIEl$u zbv4QdOJoGig{vligKpPP{74t^yZc!-Os5(R4!C ze$R87cs{<4Np%c!OqEAzG1VfgjY}LX7k3?w`H!7-SDD_{%!nfm=t@Cndb|8BSo-VbXK zLLYk2fI5uB>tQQg3tH?8cadWYC!ah;Kd=LT!HdRKrOBED3LOeLx0cPJv*7%V|Mci zt9ojGH8cHQ&-;Jgqu-}z$9qQyht;}lufgjK!&r0w$vgW_*|F^7dkrI~*@Y>&-r?nY zUJzP-hg^nnovtufwL;S=^sQmJe6<}`hDL|8)ndom(hR8rsR9dD zAPP%8>rT6BO?Fgu@f3{X`G4d5|HPXO<5%!Y_$qt_z6^K3?QkvZgjY^CjF;g*@B%y! z55fcRL--op4IhOYU>95q!!QI_z~yiubivWn4C4qKhC}ds_#I5ZOK&oaf5D6J8~8Q+ z0KN}*!0j*uSHQWT;2c;1OW==hG>kvM3-Aa$44;MDz=Sc_1)E?aoC7PM3zoydHyFmJ z;Cwg_x?nk+4KJUH25=Y-!Q=1?_!fK<_QTEa2?!wo8!E5~Ho^+%g4giHtMC~793F-5 zz_;Nh5MO-*z79Q*ftOB38+aZL!+mfs9DtKx87u_@ev7}KgJ7fzQAv;e%kpPS^q0fP!;i z1$4n#@cdHB!(P|}b(n<9U;|tVm%w`Hg0tYA@DBJJL94&QGw?J#1-+1i^Wh9=e~r!Y zBHxG?`I4G^ELi>Ono1bfg8p2tUax1(3A1RM*@9Qi1(rW)7px!`1eIN(6@z4-IAoV*?Fu59g>-bx@u$oT4c6L4w$#K*U7AA#s@0&RMnhVjKwoM zH}lHE7O~?kx3I;}*z7ruS65-hQnnj}epCo;&kd9pg^n#tT;vulUl~TX8YJCxxLQ`p zF9^3pJ6Bp64pNU;9>l9Z~EzBCyNtPq&~%u zD$RwrRW7O%qHfjNzaL@Rt8PAxw(IERn%GoT_PwZ< zQEp;lV)2OOScMSdWWUCVxS7wnYBA67V59Zil3kAc*daqn=SOwt)v)QBW%=E!xGmn1 zTjdF;p*c4CjvX`^8Ft#s)#ezJ*_|6_c+vKttF~V{xG~=_t-Du>Xk$gqcr3NJt7(N) z(M-Y!aiH#3P&E7Wj7YwX_qC+uThj8Pz&6wNwVfqBJ!PWAVg;&Rv0PPqTN7&=);&dy zNg2|UsnYb(h*t{hQioP9_DkYGv0JVx=~Q1<L*5s}y>ZEI^paP+2*sDrQmTFUqcEz^%%v#L>0NRB+4;Q8Lh_;jEEgY^$-4JJ#GB zO5%5OoQ0|6m}TX;dI(>M?P0~YtY%LGoFzk|gULG2h8ddZ%iG%3ldhA`yCe3DQ{t#Zq6ksEhHvt+6`kVaOUTGc0MNFUcN{ zFj;AJJ800D7>x#`Whpp_b7ae5Ytak;q+PT;<;a5OOl6e_XU4PBDvo!kcQ;_QQzvdsqu@8FK!=jI;5HoUi5lPqX^< z7tZ#7hG*d*JOlgS7Kk8(9Ax27r*pQ3JK^(i6Wj>Bkb~uLHoObYgi~P|EQLpD_YwFh z?1#JIE|By7ZYaU!uo*T%4`e{>T>>Y70T0uMhu~)*ae&XkUidH+U>r;sgB`F2a*%}{ z=z`_&U(Wfj!K?5J9D$#}J@6&?B76bvgd5;`s6ZJ?V1Wr4SPAce3*aa*f+O&6coCk1 zr{O7h5)Qz3;a1oORd8Sec0&o?3t3nVt6(L(NW9>m@FY9|--G+$UN`{vz;1XSTmVOj z6+8|Pz<#(J?t=7{Dv&CWDv&CWD)72gU}Vl0@lOH<@y*cGNXs|5PvVA+13BkXxoNAJ zK~VSnV%Au2Mq|KJb7r11p}jd{U=dk8IS7u)8N{jZua*7ldV70wW8AzDraDjR5iREI z=sZcHL5JjHB$A#t42c_TG}?IAH=z1%bPko1DmvQS?wt7>=+K2$TW8pq7&E7SZMJCt z>lWuXYA)gCbytU;s9Cx)n-#NNn|0JryEGAD-hwlXo5h;>oZq318P&JW)egyRaxc=f zrVeqz<^nR$k}+Lq_KB&2i15dRL@atPQtNBJ#}lAH*~N?X#5H6tm24IvyC^5dM!Fxx zAqS3UVa1eaqaW%asB4n=7$Fmmzk2e=Z8!ntdqUM?_pg`ijRsb)-s*)`|LWChu%vd! z|5{y%#uY(Lmx$0YEpZ^HTt*hh>8hIrVtYA%cB}1?+Y(|W#xpXq1-a;q_Pspn;s{*w zy=r_xFI$SIV6}+$+w;&J8lC!jI2?fV4 zOvvF_3s1O)2vSi(1(IkMfi4hJ;VX|DC1xivVhIV8YS!o@!K9$#MNW|bk}|`PqqT$- zJhk=GE3@JX#Fv2`qv{G9wVqE@&ocx>TeNjYqfj}En*4-9U m^|OFU+lnLRi5s-Aj{MX9cH|*i68l8r0 Date: Wed, 24 Feb 2021 17:43:17 -0800 Subject: [PATCH 06/12] move dev env to archive --- {dev-env => flock-archive/dev-env}/.gitignore | 0 {dev-env => flock-archive/dev-env}/README.md | 0 {dev-env => flock-archive/dev-env}/Vagrantfile | 0 {dev-env => flock-archive/dev-env}/ingress/ingress.yml | 0 {dev-env => flock-archive/dev-env}/kube-flannel.yml | 0 {dev-env => flock-archive/dev-env}/nfs-client-vals.yml | 0 6 files changed, 0 insertions(+), 0 deletions(-) rename {dev-env => flock-archive/dev-env}/.gitignore (100%) rename {dev-env => flock-archive/dev-env}/README.md (100%) rename {dev-env => flock-archive/dev-env}/Vagrantfile (100%) rename {dev-env => flock-archive/dev-env}/ingress/ingress.yml (100%) rename {dev-env => flock-archive/dev-env}/kube-flannel.yml (100%) rename {dev-env => flock-archive/dev-env}/nfs-client-vals.yml (100%) diff --git a/dev-env/.gitignore b/flock-archive/dev-env/.gitignore similarity index 100% rename from dev-env/.gitignore rename to flock-archive/dev-env/.gitignore diff --git a/dev-env/README.md b/flock-archive/dev-env/README.md similarity index 100% rename from dev-env/README.md rename to flock-archive/dev-env/README.md diff --git a/dev-env/Vagrantfile b/flock-archive/dev-env/Vagrantfile similarity index 100% rename from dev-env/Vagrantfile rename to flock-archive/dev-env/Vagrantfile diff --git a/dev-env/ingress/ingress.yml b/flock-archive/dev-env/ingress/ingress.yml similarity index 100% rename from dev-env/ingress/ingress.yml rename to flock-archive/dev-env/ingress/ingress.yml diff --git a/dev-env/kube-flannel.yml b/flock-archive/dev-env/kube-flannel.yml similarity index 100% rename from dev-env/kube-flannel.yml rename to flock-archive/dev-env/kube-flannel.yml diff --git a/dev-env/nfs-client-vals.yml b/flock-archive/dev-env/nfs-client-vals.yml similarity index 100% rename from dev-env/nfs-client-vals.yml rename to flock-archive/dev-env/nfs-client-vals.yml From 7c92010f2bf6fe3350fe27c1319b17a889ce1258 Mon Sep 17 00:00:00 2001 From: sandertyu Date: Sun, 28 Feb 2021 22:03:30 -0800 Subject: [PATCH 07/12] archive networking.md --- docs/Bare-Metal/concepts/networking.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/Bare-Metal/concepts/networking.md b/docs/Bare-Metal/concepts/networking.md index 9ff4565..35a286a 100644 --- a/docs/Bare-Metal/concepts/networking.md +++ b/docs/Bare-Metal/concepts/networking.md @@ -1,4 +1,7 @@ # Networking + +NOTE: This file is outdated for the [current galaxy cluster](https://github.com/LibreTexts/galaxy-control-repo/tree/production/router-configs). + *Relevant files: `/etc/netplan/`* *Summary: https://netplan.io/examples* We use [netplan](https://netplan.io/) to configure networking on rooster. From be590bed43f1da39fda70a62a863e477d2c59c99 Mon Sep 17 00:00:00 2001 From: sandertyu Date: Sun, 28 Feb 2021 22:04:46 -0800 Subject: [PATCH 08/12] archive nginx.md --- docs/Bare-Metal/concepts/nginx.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/Bare-Metal/concepts/nginx.md b/docs/Bare-Metal/concepts/nginx.md index 9d209bd..186cfad 100644 --- a/docs/Bare-Metal/concepts/nginx.md +++ b/docs/Bare-Metal/concepts/nginx.md @@ -1,5 +1,7 @@ # NGINX +NOTE: This file is outdated for the [current galaxy cluster](https://github.com/LibreTexts/galaxy-control-repo/tree/production/router-configs). + *Relevant files: `/etc/nginx`* *Summary: http://nginx.org/en/docs/http/load_balancing.html* From 5107c18812dbb379284e2f526cec098e6bb59c1b Mon Sep 17 00:00:00 2001 From: sandertyu Date: Sun, 28 Feb 2021 22:20:03 -0800 Subject: [PATCH 09/12] archive readme --- docs/Bare-Metal/troubleshooting/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/Bare-Metal/troubleshooting/README.md b/docs/Bare-Metal/troubleshooting/README.md index b02d45b..131da02 100644 --- a/docs/Bare-Metal/troubleshooting/README.md +++ b/docs/Bare-Metal/troubleshooting/README.md @@ -1,5 +1,7 @@ # Common Practices For Troubleshooting +NOTE: This file and others in this folder may be outdated for the [current galaxy cluster](https://github.com/LibreTexts/galaxy-control-repo/tree/production/kubernetes/). + If the troubleshooting that you are doing for a particular problem is ineffective it can largely be due to any of the following reasons: 1. You may be looking at symptoms unrelated to the problem. From df8e8470509a80f87722a3779a7824b09bb67794 Mon Sep 17 00:00:00 2001 From: sandertyu Date: Sun, 28 Feb 2021 22:22:02 -0800 Subject: [PATCH 10/12] archive updating ubuntu/kubernetes --- docs/updating-ubuntu-kubernetes.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/updating-ubuntu-kubernetes.md b/docs/updating-ubuntu-kubernetes.md index a52a7e6..e8635f3 100644 --- a/docs/updating-ubuntu-kubernetes.md +++ b/docs/updating-ubuntu-kubernetes.md @@ -1,5 +1,7 @@ # Updating Ubuntu and Kubernetes +Note: This document is mostly outdated for the [current galaxy cluster](https://github.com/LibreTexts/galaxy-control-repo/#upgrading-the-kubernetes-cluster). + This document lists the procedure for updating Ubuntu and Kubernetes on the chick nodes. From 442ef99f1611dd5ce8256743264db6899585e05c Mon Sep 17 00:00:00 2001 From: Tim Date: Mon, 1 Mar 2021 21:00:37 -0800 Subject: [PATCH 11/12] update maintenance tasks for galaxy --- docs/maintenance-tasks.md | 29 ++++++++++++++--------------- 1 file changed, 14 insertions(+), 15 deletions(-) diff --git a/docs/maintenance-tasks.md b/docs/maintenance-tasks.md index 19d0c30..dd197af 100644 --- a/docs/maintenance-tasks.md +++ b/docs/maintenance-tasks.md @@ -13,29 +13,28 @@ any issues that it finds. After the scrub is finished, it is good to also run `zpool status` to check if there is anything wrong. -This command is run on a cronjob, so there should be no -need for manual intervention. The cronjob runs at 8:00AM -the first day of every month. Gravity will also send out an +This command was previously run on a cronjob. The cronjob ran at 8:00AM +the first day of every month. Gravity would also send out an email at 8:10AM on the same day with the results. If the -scrub is fine, the email should be titled +scrub is fine, the email would be titled `[All clear] Hen monthly ZFS report`. If the title says `[POTENTIAL ZFS ISSUE]` instead, there may be something wrong with the disk, and the email contains -the `zpool status` output which you can use to debug disk -issues. Details on how the cronjob is setup are in the +the `zpool status` output which can be used to debug disk +issues. Details on how the cronjob was setup are in the private configuration repo, under `cronjob/monthly-zfs-report.py`. ## Cluster control plane upgrade The Kubernetes control plane should be upgraded regularly. -There is a cronjob sending out a triyearly reminder +There used to be a cronjob sending out a triyearly reminder (Jan, May, Sept 1st of every year) reminding you to do the upgrade. (The cronjob can be found in galaxy-control-repo.) This must be done at least once a year, otherwise the Kubernetes certificates may expire, which will [break the entire cluster](/docs/Bare-Metal/troubleshooting/KubeadmCert.md#more-complex-solution-renewing-kubeadm-certificates). -The email sent out should contain the date on which the +The email sent out contains the date on which the certificates expire. If you apply routine upgrades, certificates should be renewed automatically and this should not be an issue. If the certificates do expire, @@ -47,19 +46,19 @@ cluster upgrades indefinitely. ### Upgrading the control plane -tl;dr: Follow https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/ and upgrade the control plane, update apt packages on the nodes, then copy `/etc/kubernetes/admin.conf` on chick0 into `/home/spicy/.kube/config` on rooster. +tl;dr: Follow https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/ and upgrade the control planes, update apt packages on the nodes, then copy `/etc/kubernetes/admin.conf` on a nebula into `/home/milky/.kube/config` on gravity. Note: This will take a while and will cause some downtime. Be sure to notify users beforehand. -1. Follow the instructions in the [official cluster upgrade guide](https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/). We only have one control plane node (chick0), so follow the "Upgrade the first control plane node" secion on chick0 and ignore "Upgrade additional control plane nodes". Also follow "Upgrade worker nodes" on all other chicks. This is also a good time to [upgrade all packages on the chicks](https://github.com/LibreTexts/metalc/blob/447a459bacfbc6a29d80229e7df2f2bfb953cd7a/docs/updating-ubuntu-kubelet.md) as well, since the chicks are cordoned during the upgrade. -2. Once you verified the cluster is working using `kubectl get nodes` on rooster, copy over the newer admin certificate/key. - 1. SSH into chick0, then do `sudo cp /etc/kubernetes/admin.conf /home/spicy/.kube/config`. Also `chown spicy:spicy /home/spicy/.kube/config` to make it readable to us. - 2. Go back into rooster and do `scp chick0:.kube/config ~/.kube/config` to copy the file onto rooster. - 3. Verify `kubectl `works on both rooster and chick0 by running any kubectl command (such as `kubectl get nodes`). +1. Follow the instructions in the [official cluster upgrade guide](https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/). We have multiple control plane nodes (nebulas), so follow both the "Upgrade the first control plane node" and "Upgrade additional control plane nodes" sections. Also follow "Upgrade worker nodes" on all other worker nodes. This is also a good time to [upgrade all packages on the stars](https://github.com/LibreTexts/metalc/blob/447a459bacfbc6a29d80229e7df2f2bfb953cd7a/docs/updating-ubuntu-kubelet.md) as well, since the stars are cordoned during the upgrade. +2. Once you verified the cluster is working using `kubectl get nodes` on gravity/quantum, copy over the newer admin certificate/key. + 1. SSH into a nebula, then do `sudo cp /etc/kubernetes/admin.conf /home/milky/.kube/config`. Also `chown milky:milky /home/milky/.kube/config` to make it readable to us. + 2. Go back into gravity and do `scp nebula{1,5}:.kube/config ~/.kube/config` to copy the file onto gravity. + 3. Verify `kubectl` works on both gravity and the nebulas by running any kubectl command (such as `kubectl get nodes`). ### Renew certificates without upgrade Sometimes you want to renew the certificates without doing a proper upgrade and causing downtime. In that case, do the following: -1. Follow [the official guide](https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/#manual-certificate-renewal). tl;dr: Just run `sudo kubeadm alpha certs renew` on chick0. +1. Follow [the official guide](https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/#manual-certificate-renewal). tl;dr: Just run `sudo kubeadm alpha certs renew` on all of the nebulas. 2. Follow the same step 2 as [Upgrading the control plane](#upgrading-the-control-plane). From ca48b572da7f8073aa1e3288cc0243b66fce241f Mon Sep 17 00:00:00 2001 From: Tim Date: Tue, 2 Mar 2021 15:36:37 -0800 Subject: [PATCH 12/12] fixed wording --- docs/maintenance-tasks.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/maintenance-tasks.md b/docs/maintenance-tasks.md index dd197af..b2df817 100644 --- a/docs/maintenance-tasks.md +++ b/docs/maintenance-tasks.md @@ -7,16 +7,16 @@ This document lists all tasks that should be done regularly. * Frequency: monthly * Command: `sudo zpool scrub nest` -To execute manually, you must first ssh into blackhole +To execute manually, you must first ssh into blackhole. Scrub checks the file system's integrity, and repairs any issues that it finds. After the scrub is finished, it is good to also run `zpool status` to check if there is anything wrong. -This command was previously run on a cronjob. The cronjob ran at 8:00AM -the first day of every month. Gravity would also send out an +This command is run on a cronjob. The cronjob runs at 8:00AM +the first day of every month. Gravity also sends out an email at 8:10AM on the same day with the results. If the -scrub is fine, the email would be titled +scrub is fine, the email is titled `[All clear] Hen monthly ZFS report`. If the title says `[POTENTIAL ZFS ISSUE]` instead, there may be something wrong with the disk, and the email contains @@ -27,7 +27,7 @@ private configuration repo, under `cronjob/monthly-zfs-report.py`. ## Cluster control plane upgrade The Kubernetes control plane should be upgraded regularly. -There used to be a cronjob sending out a triyearly reminder +There is a cronjob sending out a triyearly reminder (Jan, May, Sept 1st of every year) reminding you to do the upgrade. (The cronjob can be found in galaxy-control-repo.)