This is a web system for managing servers with GPUs. It allows users to apply for instances with a specified number of GPUs by themselves. Instances of different users are isolated from each other and do not interfere with each other.
Some screenshots:
The server will use LXD to manage the GPUs and instances, please check https://github.com/shenuiuin/LXD_GPU_SERVER to set up the LXD env. Any questions on setting up the LXD env can refer the tips in this readme or open a new issue. If you don't want LXD, you need to modify the utils/util.py to set the commands. After setting the env, you need to create several LXD instances, whose names are the same as those in settings.py. You also need to set the PCI_INFO in utils/util.py of your gpus. Please exec nvidia-smi to query this info. But, better check settings.py and util.py and tailor them, if needed.
We will also use MongoDB as the database, you need to install it first.
- Setup Node 14 and yarn runtime. You can refer to https://codex.so/how-to-install-the-latest-node-js-npm-and-yarn. Note that node version should be 14.
cd client
yarn && yarn installIt's recommended to create a new conda environment (or a virtual env) for the python backend server:
conda create -n myenv python=3.8
conda activate myenv
conda install flask flask-cors numpy pymongoBoth the client and the server directories are run on the server. This client is the JS frontend, not your local machine.
- cd client and see the readme to start the Vue frontend.
- change the ip in settings.js and app.py to your server ip.
cd server && ./start.sh
cd client && ./start.shPlease check the two start.sh shells, and remove the nohup to check out the logs if needed.
We include two quota strategies in settings.py and pool.py. The user quota limits the maximum number of devices a single user can acquire. The group quota limits the maximum number of devices the whole group can obtain (when several groups share the same server, this is useful). If you don't need the group quota, change the WW_GROUP to include all user numbers and set the group quota to a big integer.
Anyway, better read some codes in settings.py, util.py, and pool.py to see how this system works. And configure it by yourselves to meet your needs. Don't worry, there is only a few codes to read. Also, you can open an issue if you need help.
Both the client and server should be run on your server. The client is actually a JavaScript frontend server (using Vue), that is, the actual access is as follows:
Your PC (the real client) -(via HTTP)-> JS/Vue frontend (the client directory of this repo) --> Python Flask server.
And, the JS frontend will provide the browser the scripts to access the Flask server.
后端app.py最后有after_request的同域名规则，如果你不想加详细的规则，可以把这个去掉，不然会报错。
#原因不明，第一次恢复是
lxc profile edit default
#在config下面加入这一行
nvidia.driver.capabilities: all
# 然后重启inst第二次恢复则是把这一行删掉，重启inst。推测是修改profile之后，会重新读取，自然而然就能恢复访问cuda。和怎么改关系不大。
不过还有可能实例重启一段时间之后才能正常访问cuda。
# 是否是mongodb崩溃
sudo systemctl status mongod
# 如果没在运行，尝试
sudo systemctl start mongod
# 如果启动失败，尝试，一般可能在机房断电重启之后发生
sudo chown mongodb:mongodb /tmp/mongodb-27017.sock
sudo chown -R mongodb:mongodb /var/lib/mongodb每一个容器的配置文件都是用的default profile
查看/修改default（不建议）
lxc profile show/edit default # 默认64G一个instance另外，也能看到所有inst的配置文件里都包含了名为root的device，该device就是root file system，所有inst都是从名为zfs-pool的池子中分配的。
在某容器中执行
df -lh也能看到该容器对zfs-pool的使用情况
lxc stop cbuild service
sudo truncate -s +10G /var/snap/lxd/common/lxd/disks/lxd.img # 加10G到存储池
sudo zpool set autoexpand=on zfs-pool
sudo zpool online -e zfs-pool /var/snap/lxd/common/lxd/disks/lxd.img
sudo zpool set autoexpand=off zfs-pool
sudo snap start lxdlxc storage info zfs-pool # 查看zfs-pool的使用情况，目前的分区是zfs-pool占用了/dev/sda下的1号分区;
lsblk # 查看所有分区基本的做法就是扩大/dev/sda分区，使用工具cfdisk
sudo cfdisk /dev/sda # 在里面选择new size，之后write(保存)，quit即可设置zfs-pool 自动扩张充满sda1
sudo zpool set autoexpand=on zfs-pool
sudo zpool online -e zfs-pool /dev/sda1那整个sda都用光了怎么办？(几乎不可能发生)。添加硬盘，参考这里
https://www.theshell.guru/how-to-increase-the-size-of-a-zfs-pool-add-drive-to-zfs-pool/
- 可以ping host server，比如ping 210.28.135.11
- dns works，ping baidu.com，会显示ping 百度的ip
可能是防火墙问题：
sudo iptables -P FORWARD ACCEPT
问题比较复杂，参考。
https://discuss.linuxcontainers.org/t/failed-to-run-dnsmasq-address-already-in-use/1132/2
check 端口53
sudo netstat -lnp | grep ":53 "我当时应该停掉了dnsmasq，安装了systemd-resolved。具体细节记不清了，systemd-resolved可能依赖dnsmasq-base。
目前我的
systemctl status dnsmasq
会显示dnsmasq inactive。
但是
sudo netstat -lnp | grep ":53 "
会显示存在一个dnsmasq监听了10.176.xxx.xxx。这个IP是lxd instance的虚拟IP段，可以通过lxd list确认。
我猜测是lxd里包含了一个dnsmasq服务用于转发lxd instances的dns请求，之后这个请求被转发到宿主systemd-resolved服务那里。因为systemd-resolved监听了127.0.0.1:53地址。