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

Removal of SQLAlchemy dependency #2

Open
teiszler opened this issue Mar 26, 2020 · 0 comments
Open

Removal of SQLAlchemy dependency #2

teiszler opened this issue Mar 26, 2020 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@teiszler
Copy link
Contributor

Originally we use a SQLAlchemy db to store all the relevant information: images, snapshots, pids of running instances, etc. I have started to pare back what we store in SQL by moving the pids into file under /var/nephele/pid, but we should be able to eventually remove this dependency by doing similar changes for images and snapshots. There are only a few pieces of important information stored for each, mainly the hash of the base image and a timestamp.

The images are already store in /var/nephele/images. If we create a subdirectory for each image which has the hash as the name, we should be able to quickly tell if an image exists simply by listing the contents of /var/nephele/images and performing a comparison. We could similarly store snapshots under /var/nephele/snapshots instead of user defined paths. The snapshots directory could have the same format with subdirectories for each image which contain the snapshots that were built from those images.

@teiszler teiszler added the enhancement New feature or request label Mar 26, 2020
@teiszler teiszler self-assigned this Mar 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant