Skip to content
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.

Deploy Issues #5001

Closed
19 tasks done
suiguoxin opened this issue Oct 22, 2020 · 0 comments
Closed
19 tasks done

Deploy Issues #5001

suiguoxin opened this issue Oct 22, 2020 · 0 comments
Assignees
Labels

Comments

@suiguoxin
Copy link
Member

suiguoxin commented Oct 22, 2020

  • P2 config copy (both in step 2/3) to /pai-deploy deployment process refine #5077
  • P2 quick-start-kubespray: requirement check should be placed before configuration.sh deployment process refine #5077
  • P2 installation document issue: checkout is placed before cd /pai deployment process refine #5077
  • P2 git clone issue: clone to an existing folder may raise error, so the code pai/kubespray may be unsuccessfully cloned. deployment process refine #5077
  • services-boot.sh:
  • kubectl setup: Deployment process refine #5085
    • apt-get update error can be ignored
    • no need to install kubectl , users can use dev-box instead
  • P3 all the user config should be together; all the generated config files are mixed in pai-deploy folder, some generated config can be reused when uninstall.
  • P3 a cluster of (4GPU, 4GPU, 2GPU) will be auto-configured as (2GPU, 2GPU, 2GPU) due to the assumption of homogeneity; (openpai-generator.py)
    • proposed solution:
      • let the user define the config instead of auto-generation;
      • check if the config meet the requirements before deployment;
  • P3 pure-CPU deployment:
    • auto-check in config;
  • --dry-run deprecated is deprecated
  • How to add and remove nodes
    • doc issue
  • -w -m -c arguments are parsed twice
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant