This is a draft guide to help people develop zos itself. It will give you also some tips and tricks to debug you changes, test new features and even test flists.
Please follow instructions under qemu on how to run your own zos in a VM
When you modify the code in the repo, build and start zos it's gonna use all zos binaries from bin/ directory. If you need to change the code again you have 2 options:\
- Either restart the node
- or
scpthe new binary to replace the one on the vm- depends on what you replacing you might need to start the service manually first. You also need
to restart the service after replacing the binary with
zinit restart <service>
- depends on what you replacing you might need to start the service manually first. You also need
to restart the service after replacing the binary with
- All the node logs can be inspected with
zinit log - If you have no access to zos node you still can inspect the logs on
https://mon.grid.tf/- You will need to request access to this. You can request access from OPS
- If you are debugging a VM. You have also multiple ways to inspect the VM logs
- If you can ssh to the zos node, inspect the logs under
/var/cache/modules/vmd/logs - You also need to try out the console of your VM it can give some valuable information
- If you can ssh to the zos node, inspect the logs under
- If above still didn't give you enough information to debug the issue I would recommend trying the same flist on a node that you have access to so you have better control/visibility