Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add network mounted volumes[WIP] #223

Open
wants to merge 25 commits into
base: develop
Choose a base branch
from
Open

Conversation

angad-k
Copy link
Member

@angad-k angad-k commented Sep 27, 2020

Now the database contents are being uploaded correctly to seaweedfs. However, on terminating gasper, because seaweedfs is running as a thread in it, seaweedfs gets terminated and the databases crash without getting a chance to close gracefully. In a recent meeting with scar and kps ,we decided the solution to this would be running seaweedfs as a docker container.

angad-k added 25 commits June 4, 2020 23:29
Add functions for setting up docker containers for seaweedfs

No breaking changes AFAIK
… to its own handler.go

move code pertaining to seaweedfs from database handler to its own handler

no breaking changes
…ervicename for seaweed containers

replace the seaweed container names' strings with types.servicename format

no breaking changes
… add persistence to seaweedfs

mount previously unmounted seaweedfs container on local storage

no breaking changes
…asper to check whether seaweedfs plugin is installed

the docker plugin that will be used to create network mounted volumes previously had to be externally installed. Now, gasper checks for and installs the plugin automatically

no breaking changes
… network mounted volumes to redis_gasper and mongodb_gasper

I have added support to create network mounted volumes using seaweedfs and its docker plugin and tried it on redis_gasper and mongodb_gasper in this commit. It still needs to be checked for stability.

Possiblity of breaking changes because of usage of network mounted volumes
Seaweedfs's volume driver wasn't stable so, shifted over to lizardfs

No breaking changes
… at some places

change seaweedfs to lizardfs at some last remaining places

no breaking changes
import seaweedfs into the codebase and use seaweedFS mounted directly instead of running seaweedFS in a container

database containers mostly can't be deployed properly after this commit
… was put in for testing

remove uneeded mysql container deployment from service-launcher.go

database containers deployment still doesn't work properly
Add functions for setting up docker containers for seaweedfs

No breaking changes AFAIK
… to its own handler.go

move code pertaining to seaweedfs from database handler to its own handler

no breaking changes
…ervicename for seaweed containers

replace the seaweed container names' strings with types.servicename format

no breaking changes
… add persistence to seaweedfs

mount previously unmounted seaweedfs container on local storage

no breaking changes
…asper to check whether seaweedfs plugin is installed

the docker plugin that will be used to create network mounted volumes previously had to be externally installed. Now, gasper checks for and installs the plugin automatically

no breaking changes
… network mounted volumes to redis_gasper and mongodb_gasper

I have added support to create network mounted volumes using seaweedfs and its docker plugin and tried it on redis_gasper and mongodb_gasper in this commit. It still needs to be checked for stability.

Possiblity of breaking changes because of usage of network mounted volumes
Seaweedfs's volume driver wasn't stable so, shifted over to lizardfs

No breaking changes
… at some places

change seaweedfs to lizardfs at some last remaining places

no breaking changes
import seaweedfs into the codebase and use seaweedFS mounted directly instead of running seaweedFS in a container

database containers mostly can't be deployed properly after this commit
… was put in for testing

remove uneeded mysql container deployment from service-launcher.go

database containers deployment still doesn't work properly
add functionality to stop databases on ctrl c which doesnt work yet

databases dont work correctly in this
@supra08
Copy link
Member

supra08 commented Oct 12, 2020

@angad-k Can you specify in the PR description what all things are WIP for this PR and what all are covered. Would be easy to review then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants