general/docs-legacy
Archived
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

improve advanced vm configuration docs

Browse Source
This commit is contained in:
ghe0 2025-02-17 18:33:49 +02:00
parent 8bbeda5895
commit bdf58f520e
Signed by: ghe0
GPG Key ID: 451028EE56A0FBB4
1 changed files with 34 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
src/cloud/advanced.md
View File

@ -2,6 +2,39 @@
This page is oriented towards power users that would like to know more about the mechanics of the DeTEE platform and would like to experiment by adding their own kernel, their own initrd or building OS templates for their own distribution or with their own apps. This page is oriented towards power users that would like to know more about the mechanics of the DeTEE platform and would like to experiment by adding their own kernel, their own initrd or building OS templates for their own distribution or with their own apps.
## Add IPv6 to VM
As long as the node operator offered an IPv6 range on his node, you will be able to deploy a VM with IPv6 support. This was not added to the predefined list of parameters for the CLI, however you can deploy using the `--from-yaml` flag, that allows you to add IPv6 support. More examples can be found in `/root/.detee/samples/`.
To test this out, run:
```
detee-cli vm deploy --from-yaml /root/.detee/samples/new_vm/public_ipv4_and_ipv6.from-yaml
```
After that, SSH into the VM and test IPv6 connectivity. Example:
```
root@24ddd97f135b /# detee-cli vm deploy --from-yaml /root/.detee/samples/new_vm/public_ipv4_and_ipv6.yaml
Node price: 0.00002/unit/minute. Total Units for hardware requested: 43. Locking 0.258 LP (offering the VM for 5 hours).
Injecting disk encryption key into VM. This will take a minute. Do not interrupt.
VM CREATED! To ssh, run the following command:
ssh -p 22 root@173.234.136.154
root@24ddd97f135b /# ssh -p 22 root@173.234.136.154
[root@my-public-vm-01 ~]# ip -c -br a
lo UNKNOWN 127.0.0.1/8 ::1/128
enp0s1 UP 173.234.136.154/27 2a0d:3003:b666:a00c:2::11/64 fe80::fcc8:b0ff:fe12:c285/64
[root@my-public-vm-01 ~]# ping 2606:4700:4700::1111
PING 2606:4700:4700::1111 (2606:4700:4700::1111) 56 data bytes
64 bytes from 2606:4700:4700::1111: icmp_seq=1 ttl=57 time=14.9 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=2 ttl=57 time=13.4 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=3 ttl=57 time=14.3 ms
64 bytes from 2606:4700:4700::1111: icmp_seq=4 ttl=57 time=13.1 ms
^C
--- 2606:4700:4700::1111 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 13.136/13.931/14.892/0.697 ms
[root@my-public-vm-01 ~]#
```
## Kernel and DTRFS ## Kernel and DTRFS
DeTEE VMs currently run using the latest stable version of the kernel. This is required in order to guarantee that the SNP features are enabled. As the progress moves forward, we will also offer the LTS kernel as part of our default feature set. DeTEE VMs currently run using the latest stable version of the kernel. This is required in order to guarantee that the SNP features are enabled. As the progress moves forward, we will also offer the LTS kernel as part of our default feature set.
@ -106,7 +139,7 @@ Logout of SSH and scp `/tmp/os_template.fsa` to your machine:
## Experimenting on your own ## Experimenting on your own
If you feel like experimenting, the CLI allows you to deploy a VM using your own kernel and your own OS template. This can be done using `detee-cli vm deploy --from-yaml` and passing the path to your config. Examples can be found in `~/.detee/cli/new_vm_samples/` If you feel like experimenting, the CLI allows you to deploy a VM using your own kernel and your own OS template. This can be done using `detee-cli vm deploy --from-yaml` and passing the path to your config. Examples can be found in `~/.detee/samples/new_vm/`
This is how the yaml file must look: This is how the yaml file must look:
```yaml ```yaml