mravi/uncloud
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

++notes

Browse source
This commit is contained in:
Nico Schottelius 2020-05-05 15:19:04 +02:00
parent 99a18232aa
commit e3b28354fe
1 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
uncloud_django_based/uncloud/doc/README-how-to-configure-remote-uncloud-clients.org
View file

@ -10,6 +10,7 @@
| SSH -L tunnel | All nodes can use [::1]:5432 | SSH setup can be fragile | | SSH -L tunnel | All nodes can use [::1]:5432 | SSH setup can be fragile |
| ssh djangohost manage.py | All DB ops locally | Code is only executed on django host | | ssh djangohost manage.py | All DB ops locally | Code is only executed on django host |
| https + token | Rest alike / consistent access | Code is only executed on django host | | https + token | Rest alike / consistent access | Code is only executed on django host |
| from_django | Everything is on the django host | main host can become bottleneck |
** remote vs. local Django code execution ** remote vs. local Django code execution
- If manage.py is executed locally (= on the client), it can - If manage.py is executed locally (= on the client), it can
check/modify local configs check/modify local configs
@ -19,3 +20,9 @@
- Remote execution (= on the primary django host) can acess the db - Remote execution (= on the primary django host) can acess the db
via unix socket via unix socket
- However remote execution cannot check local state - However remote execution cannot check local state
** from_django
- might reuse existing methods like celery
- reduces the amount of things to be installed on the client to
almost zero
- follows the opennebula model
- has a single point of failurebin