4 ms·

We built a runnable jupyter notebook website. Would someone be able to take a look and give us some feedback? https://datacabinet.systems https://datacabinet.s

We built a runnable jupyter notebook website. Would someone be able to take a look and give us some feedback? https://datacabinet.systems https://datacabinet.systems We are VM based for now but are moving to be kubernetes based to make sharing better. Our initial market is classrooms.

asdfman123 7y ago
There are a few basic UI problems I ran into immediately. You should focus on that instead of rearchitecting things. It needs to look sleeker, too. Pay some designer to create a new design for you. Like I can't add a project. It says "To create project Please wait till hard drive button turn green." I don't know what that means. You've lost my attention.
- airocker 7y ago
  Thanks. We are doing some enhancements. Here is some initial screen: https://mondaytest.datacabinet.systems/ https://mondaytest.datacabinet.systems/ system but the page inside is still the same. We have an elaborate design done.
  - airocker 7y ago
    Right now, for VMs we make a hard drive(mkfs, install things) for every user that takes some initial time. We will fix that in the kubernetes version.
localhost 7y ago
Something to be aware of (and a general comment about k8s in general) is that k8s is not suitable for use in hostile multi-tenant scenarios like the one that you're describing. Once an attacker escapes from the container (see HN archives for lots of examples of this), they can p0wn the entire cluster. Jessie Frazelle has a great post on this: https://blog.jessfraz.com/post/hard-multi-tenancy-in-kubernetes/ https://blog.jessfraz.com/post/hard-multi-tenancy-in-kuberne... There are expensive ways to deal with this today, e.g., running each user isolated in a separate VM. Hopefully we will have better solutions in the near future.
- airocker 7y ago
  We were starting to work on disabling kubernetes cluster access. We will try the steps in the post.

asdfman123 7y ago

There are a few basic UI problems I ran into immediately. You should focus on that instead of rearchitecting things. It needs to look sleeker, too. Pay some designer to create a new design for you. Like I can't add a project. It says "To create project Please wait till hard drive button turn green." I don't know what that means. You've lost my attention.

airocker 7y ago
Thanks. We are doing some enhancements. Here is some initial screen: https://mondaytest.datacabinet.systems/ https://mondaytest.datacabinet.systems/ system but the page inside is still the same. We have an elaborate design done.
- airocker 7y ago
  Right now, for VMs we make a hard drive(mkfs, install things) for every user that takes some initial time. We will fix that in the kubernetes version.

localhost 7y ago

Something to be aware of (and a general comment about k8s in general) is that k8s is not suitable for use in hostile multi-tenant scenarios like the one that you're describing. Once an attacker escapes from the container (see HN archives for lots of examples of this), they can p0wn the entire cluster. Jessie Frazelle has a great post on this: https://blog.jessfraz.com/post/hard-multi-tenancy-in-kubernetes/ https://blog.jessfraz.com/post/hard-multi-tenancy-in-kuberne... There are expensive ways to deal with this today, e.g., running each user isolated in a separate VM. Hopefully we will have better solutions in the near future.

airocker 7y ago
We were starting to work on disabling kubernetes cluster access. We will try the steps in the post.