Preparing a cloud image

WARNING This information is deprecated and has been moved to:https://quantum-mobile.readthedocs.io/

General guidelines

For the server to build the VM, choose e.g. 2 CPUs with 4GB of RAM
- Your configuration may also be the standard configuration shown to users creating a VM using your image (to figure out?)
- You won't need it for long, so price for CPU/RAM is of no concern
Exemplary metadata:
- name: quantum-mobile-20-05-0 (GCP only allows alphanumeric characters + dashes)
- family: quantum-mobile
- description:
```
 Quantum Mobile Cloud Edition Server v20.05.0
 See https://github.com/marvel-nccr/quantum-mobile-cloud-edition
```

Create new keypair from the GUI - note: will always be added to ubuntu user
If you intend to publish the image, follow AWS instructions to remove system SSH keys:
sudo shred -u /etc/ssh/*_key /etc/ssh/*_key.pub
List image publicly: After creation, edit the properties and select "public"

GCP lets you create the SSH keypair by yourself:
- Create new SSH keypair on your machine.
- Edit the user@server bit at the end of the public key to user "ubuntu" (GCP detects this user and adds the SSH public key for this user in the VM)
- add public key to VM
VM IP seems to be stable even between stop/start of VM
Creating the image
- GCP distinguishes between "Machine images" (private) and "Images" (can be public). You want the second option.

List image publicly: (not sure whether there is a way to do this via the GUI)

Paste command

 gcloud compute images add-iam-policy-binding quantum-mobile-20-05-0 \
     --member='allAuthenticatedUsers' \
     --role='roles/compute.imageUser'

Image pricing (for us to host it):
- magnetic: 8.5c/GB/month (GCP)
Disk pricing (for users):
- magnetic: 4c/GB/month (GCP), 2.5c/GB/month (AWS)
- SSD: 10c/GB/month (AWS)