This repository was archived by the owner on Aug 2, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 19
Virtual folder API #28
Labels
Milestone
Comments
Let's consider using Alluxio |
achimnol
added a commit
to lablup/backend.ai
that referenced
this issue
May 16, 2017
* refs lablup/backend.ai-manager#28, lablup/backend.ai-manager#31 * Now we have a common JSON object reference. (WIP)
achimnol
added a commit
that referenced
this issue
Aug 23, 2017
* Now manager + gateway runs on multiple CPU cores with sane transaction semantics. Thanks to aiotools! - It no longer depends on Redis as a pub-sub broker nor a database. All communications are done via ZeroMQ with no centralized queue server. - Redis is used only for per-keypair rate-limiting. * Now the manager searches available agent to spawn new containers based on available memory / CPU / GPU capacity units. No more hard-coded instance types! * The db schema is now prepared for multi-container kernel sessions. - User-facing APIs now use "session ID" which is directed to the master container of the given session. - Each container has unique "kernel ID" and managed individually. * Replace asyncpg + asyncpgsa with aiopg for better SQLAlchemy supports (especially custom type decorators). * TODOs - Stabilize accounting of used/available resource units. - Still some parts are confused of session/kernel IDs...
achimnol
added a commit
that referenced
this issue
Nov 17, 2017
achimnol
added a commit
that referenced
this issue
Nov 17, 2017
achimnol
added a commit
that referenced
this issue
Nov 17, 2017
Marking this as done — extension will be separate issues. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Provide a virtual folder API. Users can create virtual folders with limited storage and mount them when launching kernel sessions by passing the list of virtual folders via options.
/home/work
of kernel containersWe should keep each virtual folder exclusively mounted. (not shared among multiple kernels even for a single user) -- release this limitation later? (it's NFS's responsibility to keep filesystem consistency anyway)The text was updated successfully, but these errors were encountered: