From charlesreid1

m (Replacing charlesreid1.com:3000 with git.charlesreid1.com)
 
(12 intermediate revisions by the same user not shown)
Line 5: Line 5:
Current stage: spy project (preparing Dockerfiles, testing additional components before yeti deployment)
Current stage: spy project (preparing Dockerfiles, testing additional components before yeti deployment)


===dashboards===
===aws things===


current status: resolved to use mongodb
AWS writeup for DIB lab group: [[AWS Writeup]]


next step goals:
Amazon VPC and VPN
* run mongodb query in javascript
* set up private test node with vpc
* collect more data
* if no internet gateway, how can we update? if have internet gateway, can anyone accses necessarily?
* visualize data for single chart/single time series with D3
* networking patterns - private and public subnet, single public subnet, one gateway with internet for mult. subnets
* visualize more data using [[Grafana]]
* use this as a testbed for banana pi hardware


toy problem:
===monitoring and dashboards===
* 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:
netdata: [[Netdata]]
* understand/monitor/understand large complex systems
* adding python metrics: https://github.com/firehol/netdata/blob/master/python.d/sensors.chart.py
* minimize time to set up database, add metrics, visualize, gain insight, repeat
* workflow? need to restart?
* accessing via api - nomenclature/special considerations
* file size, download progress, etc. from python


toy problem:
prometheus: [[Prometheus]]
* instrumented TSP or other
* how to structure data directory
* on the 1st of the month:
* find any data older than 1 month
* archive it and put it in a bucket
* purge data from system
 
grafana: [[Grafana]]
* building more complex dashboards
* sharing dashboards


===toy problem goal===
===toy problem goal===


instrument a code, instrument a node, combine collected data about both
sourmash - dive into the source and instrument it.
* 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
Python signals library - send a signal 10 to the running program, and that bumps it into the netdata state, where it grabs values of different variables?


focus on greenfield deployments - install netdata, collect stats, visualize them
focus on greenfield deployments - install netdata, collect stats, visualize them
Line 51: Line 55:
more calendars:
more calendars:
* wikipedia article edit calendars
* wikipedia article edit calendars
* hourly calendar?
* dates... color dimension, pref. binary...
 
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 [http://charlesreid1.github.io/a-shrubbery/educationca/ a shrubbery]
Fix [http://charlesreid1.github.io/a-shrubbery/educationca/ a shrubbery]
Line 69: Line 67:
* Bots
* Bots
* bootstrap table presenting results of Rubik's Cube investigation - [[Rubiks Cube/Bootstrap]]
* bootstrap table presenting results of Rubik's Cube investigation - [[Rubiks Cube/Bootstrap]]
* aws


===bots===
===bots===


Still chuggin with the charlesreid1 spreadsheet. Slogging through the litany of wiki pages. Google Sheets. https://charlesreid1.com:3000/charlesreid1/charlesreid1-awesome
Still chuggin with the charlesreid1 spreadsheet. Slogging through the litany of wiki pages. Google Sheets. https://git.charlesreid1.com/charlesreid1/charlesreid1-awesome


With the deployment of charlesreid1 bot, we want to take the time to do it more thoroughly:
With the deployment of charlesreid1 bot, we want to take the time to do it more thoroughly:
Line 125: Line 124:
* 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.

Latest revision as of 03:10, 9 October 2019

overarching goal

2018/Data Project

Current stage: spy project (preparing Dockerfiles, testing additional components before yeti deployment)

aws things

AWS writeup for DIB lab group: AWS Writeup

Amazon VPC and VPN

  • set up private test node with vpc
  • if no internet gateway, how can we update? if have internet gateway, can anyone accses necessarily?
  • networking patterns - private and public subnet, single public subnet, one gateway with internet for mult. subnets
  • use this as a testbed for banana pi hardware

monitoring and dashboards

netdata: Netdata

prometheus: Prometheus

  • how to structure data directory
  • on the 1st of the month:
  • find any data older than 1 month
  • archive it and put it in a bucket
  • purge data from system

grafana: Grafana

  • building more complex dashboards
  • sharing dashboards

toy problem goal

sourmash - dive into the source and instrument it.

Python signals library - send a signal 10 to the running program, and that bumps it into the netdata state, where it grabs values of different variables?

focus on greenfield deployments - install netdata, collect stats, visualize them

d3 viz

10 visualizations:

more calendars:

  • wikipedia article edit calendars
  • dates... color dimension, pref. binary...

Fix a shrubbery

Also see D3x10

blog posts

bots

Still chuggin with the charlesreid1 spreadsheet. Slogging through the litany of wiki pages. Google Sheets. https://git.charlesreid1.com/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

Bots/Charlesreid1

Bots/Instrumentation

apollo bots:

  • 14/15/16/17
  • incorporate lunar surface dialogue

apollo references:

Category:Bots

Bots/New Apollo

genealogy

Genealogy photos:

  • Photos cropped/organized by family
    • 2011
    • 2017
    • Rename scheme
    • Notes - 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.

back burner

See 2018/February#back burner

complete

flags