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

Persistent Storage with EFS #21

Open
dzerhusen opened this issue Jun 18, 2021 · 0 comments
Open

Persistent Storage with EFS #21

dzerhusen opened this issue Jun 18, 2021 · 0 comments

Comments

@dzerhusen
Copy link

dzerhusen commented Jun 18, 2021

Hello,
is there a way to configure fargateSpawner with EFS ?
I managed to get fargateSpawner running spawning Labs from a TaskDefinition using one EFS with an AccessPoint.
Resulting in all spawning Labs have the same storage dir.

I currently see two ways:
1.
Configuring Jupyterhub/FargateSpawner to redirect to a folder under the one EFS for example. (EFS is mounted on /home/joyvan)
/home/joyvan/user1 and /home/joyvan/user2 . The user1 or user2 dir must be created somewhere.
This would result in having one EFS for all and data accessible for everyone but users land in their home directory which is persistent. This is still okay for my solution.

Prettier:
2.
Configuring Jupyterhub/FargateSpawner to create an accessPoint for the known EFS for every User.
This will result in having one EFS but data is not accessible for everyone because of the accessPoints. But i need to set somewhere the new mounting configuration and it seems i am not able to do it with the c.FargateSpawner.get_run_task_args and the overrides.

   'cluster': cluster,
    'taskDefinition': runtaskTaskdefinitionArn,
    'count': 1,
    'overrides': {
        'containerOverrides': [{
....cutted

Depending its no even possible to override mount configs by the AWS RunTask or StartTask API.

The solutions seems to need more or less code implementations, which i really want to avoid.
Is there maybe already a solution?

Some help would be appreciated, thank you.

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

No branches or pull requests

1 participant