2018/March: Difference between revisions
From charlesreid1
(→bots) |
|||
| Line 125: | Line 125: | ||
* creating a second node that's a complete and total backup of the first. | * creating a second node that's a complete and total backup of the first. | ||
* in the process of doing this, we're going to have a lot of questions to answer and software to fix. | * in the process of doing this, we're going to have a lot of questions to answer and software to fix. | ||
* letsencrypt certificate generation | * letsencrypt certificate generation | ||
* ssh | |||
We are one step toward that goal with scripts that are automating site updates, committing to git repos, pulling latest versions of data, etc. | We are one step toward that goal with scripts that are automating site updates, committing to git repos, pulling latest versions of data, etc. | ||
Revision as of 08:23, 3 March 2018
overarching goal
Current stage: spy project (preparing Dockerfiles, testing additional components before yeti deployment)
dashboards
current status: resolved to use mongodb
next step goals:
- run mongodb query in javascript
- collect more data
- visualize data for single chart/single time series with D3
- visualize more data using Grafana
toy problem:
- use instrumented traveling salesman problem (or rubiks cube code, or some other project euler code)
- proof of concept use of monitoring
- greenfield deployment of netdata
goal:
- understand/monitor/understand large complex systems
- minimize time to set up database, add metrics, visualize, gain insight, repeat
toy problem:
- instrumented TSP or other
toy problem goal
instrument a code, instrument a node, combine collected data about both
- pick a computationally intensive problem
- pick a node platform
- collect the data - mongodb
instrument a TSP problem code, show a proof of concept of what we want to be able to record/measure/visualize
focus on greenfield deployments - install netdata, collect stats, visualize them
d3 viz
10 visualizations:
wiki edits calendar visualizationhttps://charlesreid1.com/wiki_calendar and D3/Calendargit calendar visualizationhttps://charlesreid1.com/git_calendar and D3/Calendargame of lifehttps://charlesreid1.com/life and D3/Life- map series: Javascript/Maps
- leaflet maps with click behavior
- leaflet maps linked to c3/d3 charts
- twin linked leaflet maps
more calendars:
- wikipedia article edit calendars
- hourly calendar?
back burner:
- time series for code profiling D3/Time Series
- brushable time series chart D3/Brushable Time Series
- mongodb-javascript connection
- bots or scraped data daily viz
Fix a shrubbery
Also see D3x10
blog posts
- Project Euler/502
- D3/Life visualization
- Bots
- bootstrap table presenting results of Rubik's Cube investigation - Rubiks Cube/Bootstrap
bots
Still chuggin with the charlesreid1 spreadsheet. Slogging through the litany of wiki pages. Google Sheets. https://charlesreid1.com:3000/charlesreid1/charlesreid1-awesome
With the deployment of charlesreid1 bot, we want to take the time to do it more thoroughly:
- bot instrumentation
- dashboard
- monitoring bot status
- statistics
- display latest tweet
- bot dashboard built with grafana
apollo bots:
- 14/15/16/17
- incorporate lunar surface dialogue
apollo references:
- link to apollo 11 audio: https://www.nasa.gov/mission_pages/apollo/40th/a11_audio_db.html
- Spacelog (mercury, gemini, pre-11 apollo missions): http://spacelog.org/
- apollo surface journals: https://history.nasa.gov/alsj/main.html
genealogy
Genealogy photos:
- Photos cropped/organized by family
20112017Rename schemeNotes - A2k11- Notes - R2k11
- Notes - A2k17
- Notes - K2k17
- Notes - R2k17
- Send email to fam with link on Dropbox
Writing:
- Pauline and Bruce chapters
- Historical research planning
stretch goal
test backup and restore scripts
automate automate automate
- use an AWS node or a GC node to actually test the backups, start to finish.
- creating a second node that's a complete and total backup of the first.
- in the process of doing this, we're going to have a lot of questions to answer and software to fix.
- letsencrypt certificate generation
- ssh
We are one step toward that goal with scripts that are automating site updates, committing to git repos, pulling latest versions of data, etc.
Now that we are familiar with subprocess for non-trivial tasks, we can move forward with scripts to automate testing.