Issues · hpc-team / HPCasCode · GitLab

edgecases for COLD-drain-jobs and auto-resumes

#33 · opened Jul 24, 2020 by Andreas Hamacher
- CLOSED
- 0
updated Sep 03, 2020
hypervisor maintenance

#31 · opened Jul 08, 2020 by Andreas Hamacher Automatic rolling node updates Future Releases
- CLOSED
- 0
updated Sep 03, 2020
humans do not work at night

#30 · opened Jun 12, 2020 by Andreas Hamacher Automatic rolling node updates Phase1
- 0
updated Jun 12, 2020
run ansible --check and output inconsistencies for consumption by autoupdate

#29 · opened Jun 11, 2020 by Andreas Hamacher Automatic rolling node updates Doing Phase1
- CLOSED
- 1
updated Jun 12, 2020
enable kernel version pinning for ubuntu

#28 · opened Jun 11, 2020 by Andreas Hamacher merge back cvl@uwa and have it as a valid third cluster on the pipeline
- 0
updated Jun 11, 2020
automated hypervisor_upgrade while rolling upgrades

#27 · opened Jun 05, 2020 by Andreas Hamacher Automatic rolling node updates Future Releases
- CLOSED
- 1
updated Sep 03, 2020
Readme improvements

#25 · opened May 17, 2020 by Andreas Hamacher
- CLOSED
- 0
updated May 20, 2020
(to be discussed) Develop a heuristic to maximize uptame and minimize user impact

#24 · opened May 17, 2020 by Andreas Hamacher Automatic rolling node updates Phase 3
- CLOSED
- 1
updated Sep 03, 2020
Documentation

#23 · opened May 17, 2020 by Andreas Hamacher Automatic rolling node updates Phase 3
- 0
updated May 17, 2020
think about max-retry time e.g. stop trying after 5 failures

#22 · opened May 17, 2020 by Andreas Hamacher Automatic rolling node updates Phase 2
- 0
updated May 17, 2020
a mechanism to pause the whole thing during maintenance or while bugfixing a playbook

#21 · opened May 17, 2020 by Andreas Hamacher Automatic rolling node updates Phase1
- 0
updated May 17, 2020
a mechanism to update the repository and playbook

#20 · opened May 17, 2020 by Andreas Hamacher Automatic rolling node updates Phase 2
- 0
updated May 17, 2020
a mechanism to online update the nodelist to be able to add nodes to the mechanism

#19 · opened May 17, 2020 by Andreas Hamacher Automatic rolling node updates Phase 2
- 0
updated May 17, 2020
Canary testing: new commit( remember sha) , test canary nodelist first, only when that one passes then role out largely

#18 · opened May 17, 2020 by Andreas Hamacher Automatic rolling node updates Phase1
- 0
updated May 17, 2020
Host blacklist, whitelist and canarilist ( crash if a node is blacklisted AND ( white or canary)) just as an extra safety mechanism for e.g. sql and mgmtnodes

#17 · opened May 17, 2020 by Andreas Hamacher Automatic rolling node updates Phase1
- 1
updated Jul 22, 2020
hook up a change detector, capable of returning ERROR, GOOD, HotChange-nodelist or DrainChange-nodelist

#16 · opened May 17, 2020 by Andreas Hamacher Automatic rolling node updates Phase1
- CLOSED
- 0
updated Jun 16, 2020
use ansible vault

#15 · opened May 17, 2020 by Andreas Hamacher Automatic rolling node updates Phase1
- 0
updated May 17, 2020
autoupdate test-cases

#14 · opened May 17, 2020 by Andreas Hamacher Automatic rolling node updates Phase1 To Do
- 1
updated May 26, 2020
autoupdate slack hookup

#13 · opened May 17, 2020 by Andreas Hamacher Automatic rolling node updates Doing Phase1
- 0
updated Jun 01, 2020
playbook or role tagging with HotChange and DrainChange

#12 · opened May 17, 2020 by Andreas Hamacher Automatic rolling node updates Phase1
- CLOSED
- 0
updated May 25, 2020