summaryrefslogtreecommitdiffstats
path: root/docs/vision.txt
diff options
context:
space:
mode:
authorSuren A. Chilingaryan <csa@suren.me>2019-10-06 05:00:55 +0200
committerSuren A. Chilingaryan <csa@suren.me>2019-10-06 05:00:55 +0200
commitba144fab071258a97cf3c42a0defeb0aae41a353 (patch)
tree2e738d4e4774d754b56d79021cc8781b3c0835a5 /docs/vision.txt
parentefe4b9bbe3c9cb950378de9697eed2030ac49ca2 (diff)
downloadands-ba144fab071258a97cf3c42a0defeb0aae41a353.tar.gz
ands-ba144fab071258a97cf3c42a0defeb0aae41a353.tar.bz2
ands-ba144fab071258a97cf3c42a0defeb0aae41a353.tar.xz
ands-ba144fab071258a97cf3c42a0defeb0aae41a353.zip
Document latest problems with docker images and resource reclaimation, add docker performance checks in the monitoring scripts, helpers to filter the logs
Diffstat (limited to 'docs/vision.txt')
-rw-r--r--docs/vision.txt19
1 files changed, 19 insertions, 0 deletions
diff --git a/docs/vision.txt b/docs/vision.txt
new file mode 100644
index 0000000..bfef287
--- /dev/null
+++ b/docs/vision.txt
@@ -0,0 +1,19 @@
+Ands v.2
+========
+ - Try overlay2 storage driver (LVM is used in Ands v.1). Check also further docker configuration options: 'cgroup-driver', ...
+ - Integrate fast Ethernet and use conteiner native networking. OpenVSwitch is slow and causes problems.
+ - Do not run pods on Master nodes, but Gluster and a few databases pods (MySQL) are OK (multiple reasons, especially mounting a lot of Gluster Volumes)
+ - Object Storage should be integrated, either Gluster Block is ready for production or we have to use Ceph as well
+ - Automatic provisioning would be much better then handling volumes trough Ands. Basically, this will render Ands redundant. We can switch to Helm, etc.
+ But, we need ability to easily understand which volume belong to which pod/namespace and automatically kill redundant volumes.
+
+Questions
+=========
+ - Updates to cluster configuration (evaluate current load, etc.)? Non-scheduling masters? Something with storage? Specify appropriate node parameters
+ - Shall we switch to plain Kubernetes or keep using OpenShift. Discussion (just take a not about security - it is right to ban containers running as
+ root, otherwise hazard to our data model):
+ https://cloudowski.com/articles/10-differences-between-openshift-and-kubernetes/
+ - Can we find a good distributed storage for data-intensive databases. Current, slave-master model requires too much manual attention.
+ - Can we find a way to run GUI applications in containers? Kind of having CUDA profiller would be nice.
+ - Think about monitoring. Probably SNMP + it would be nice to have some kind of SQL database with perofrmance metrics.
+