microsoft / pai

Resource scheduling and cluster management for AI

Home Page:https://openpai.readthedocs.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Every one can clone other's job, seems not safe

HaoLiuHust opened this issue · comments

Organization Name:

Short summary about the issue/question:
Every user can clone other's job , is it by design?

Brief what process you are following:

How to reproduce it:
in the job list, clone other user's job

OpenPAI Environment:

  • OpenPAI version: v1.8.0
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Hardware (e.g. core number, memory size, storage size, GPU type etc.):
  • Others:

Anything else we need to know:

I think it's by design, even if cloned, the job won't run properly because the private data is inaccessible.

I think it's by design, even if cloned, the job won't run properly because the private data is inaccessible.

I guess they can access the data by mount nfs.. by the way, if every one can clone other's job, it's conflict with the markentplace private/public policy

I guess they can access the data by mount nfs.

This is an inherent problem with NFS and doesn't seem to be fixed by pai.

if every one can clone other's job, it's conflict with the markentplace private/public policy

You can only see which image and startup command was used in the job, it doesn't matter, the marketplace can also include documentation if you like.