diff options
author | Wild Kat <wk@futureinquestion.net> | 2018-03-20 23:15:34 +0100 |
---|---|---|
committer | Wild Kat <wk@futureinquestion.net> | 2018-03-20 23:15:34 +0100 |
commit | 6f672654c7e725bc828b6577297b86d501780c50 (patch) | |
tree | cf29588894d0c071f0e6b393671c84b7dd605163 /TODO.md | |
parent | baee367bfec7ec5241ad7e893de7df8ea7eec1e7 (diff) | |
parent | e7075d18e055613cb0324f0fc8eecfe7adeeac56 (diff) |
refactor snr support into dcnos model
Diffstat (limited to 'TODO.md')
-rw-r--r-- | TODO.md | 52 |
1 files changed, 29 insertions, 23 deletions
@@ -1,23 +1,29 @@ -# refactor core - * move state from memory to disk, sqlite probably - * allows us to retain stats etc over restart - * simplifies code - * keep only running nodes in memory - * negligible I/O cost, as majority is I/O wait getting config - -# separate login to owon package - * oxidized-script is not only use-case - * it would be good to have minimal package used to login to routers - * oxidized just one consumer of that functionality - * what to do with models, we need model to know how to login. Should models be separated to another package? oxidized-core, oxidized-models and oxidized-login? - * how can we allow interactive login in oxidized-login? With functional VTY etc? REPL loop in input/ssh and input/telnet? - -# thread number - * think about algo - * if job ended later than now-iteration have rand(node.size) == 0 to add thread - * if now is less than job_ended+iteration same chance to remove thread? - * should we try to avoid max threads from being hit? (like maybe non-success thread is pulling average?) - -# docs, testing - * yard docs - * minitest tests +# To Do + +## refactor core + +* move state from memory to disk, sqlite probably +* allows us to retain stats etc over restart +* simplifies code +* keep only running nodes in memory +* negligible I/O cost, as majority is I/O wait getting config + +## separate login to own package + +* oxidized-script is not only use-case +* it would be good to have minimal package used to login to routers +* oxidized just one consumer of that functionality +* what to do with models, we need model to know how to login. Should models be separated to another package? oxidized-core, oxidized-models and oxidized-login? +* how can we allow interactive login in oxidized-login? With functional VTY etc? REPL loop in input/ssh and input/telnet? + +## thread number + +* think about algo +* if job ended later than now-iteration have rand(node.size) == 0 to add thread +* if now is less than job_ended+iteration same chance to remove thread? +* should we try to avoid max threads from being hit? (like maybe non-success thread is pulling average?) + +## docs, testing + +* yard docs +* minitest tests |