| 13 May 2019 |
 lhw | no it will use the rbd gateway straight on the mons. so you define a network disk and proxmox uses that as disk for the vms. so does ovirt | 16:20:05 |
| lhw | dont ever use s3 for something like this. even with hacks like s3backer etc. the performance is abysmal | 16:20:36 |
| lhw | https://pve.proxmox.com/wiki/Storage:_RBD | 16:21:01 |
 cdknight | On a side note, as a noob, would the S3 be practical for backups? | 16:24:54 |
| cdknight | I mean, backups in general in my homelab | 16:25:05 |
| lhw | oh yea definitely. i use duplicityto backup to an offsite s3 | 16:25:39 |
| cdknight | Okay, good to know. Does rbd work with oVirt as well? | 16:28:26 |
| lhw | yes but it uses either a different daemon for the creation of disks (cinder from openstack) or iscsi | 16:30:57 |
| lhw | libvirt though supports ceph directly | 16:31:12 |
| cdknight | That's interesting. I might write my own virtualization platform someday, using libvirt, so that will be useful. | 16:31:46 |
| lhw | depends on how you scale your vms. i think libvirt is more than enough if you only have one node | 16:32:55 |
| cdknight | Well how would libvirt work with more than one node for HA? | 16:33:31 |
| cdknight | I'm not too experienced ATM concerning that, I only have one server at this point | 16:33:46 |
| lhw | imo if you have more than one node you could just straight up use openstack. ovirt seems like a weird stopgap to me. but there might be others who know more | 16:35:10 |
| cdknight | Could I use openstack with one node and then expand it later (I currently have one server but I will be getting one more soon)? I find that oVirt with one node isn't that great because it uses up 4 gigs of RAM for the self hosted engine VM. Also, what are the differences between oVirt and OpenStack? | 16:37:15 |
| lhw | not gonna lie. openstack is a lot to learn. the amount of components alone https://www.openstack.org/software/project-navigator/openstack-components requires a good read | 16:39:43 |
| lhw | with your vms on ceph you can of course easily move them later to openstack. not without downtime but with minimum hazzle | 16:40:22 |
| lhw | so you could start out with libvirt and then move them later | 16:40:32 |
| cdknight | Well, does libvirt scale well and run on multiple nodes easily, or does it involve a lot of work? I'm not too expereinced on what I should be looking for for multiple node VM systems, but maybe you could give me a pointer. | 16:42:20 |
| lhw | each libvirt installation by itself does not know other instances. there ways around that with additional services but i wouldnt recommend it. | 16:45:40 |
| lhw | Redacted or Malformed Event | 16:46:40 |
| lhw | you probably could do a ssh m1 virsh dump-xml | ssh m2 virsh define - but i wouldn't do that. as i said its mostly for the first setup | 16:46:57 |
| cdknight | Yes, I think I could work with that. Also, do you know how SPICE works with libvirt? | 16:48:37 |
| lhw | same as vnc but better | 16:49:20 |
| lhw | virsh also offers a console if you use linux. straight up throws you on tty1. its absolutely great | 16:49:41 |
| lhw | oh i see mist.io exists. that might work for you. the ce version is free and supports multiple libvirt instances | 16:50:07 |
| cdknight | I'll take a look at mist.io, but do you know what spiceproxy is like? Is it slower? I will be using a GUI on some of my VMs so I guess virsh might not be an option. | 16:51:37 |
| lhw | never used proxmox myself. the virt-manager from libvirt does have an in-built spice client though. and virt-viewer can also be run outside of virt-manager | 16:54:58 |
| lhw | works just fine over the network. a lot better performing than vnc. thats for sure | 16:55:11 |
| cdknight | Well, I was thinking SPICE on the internet, hence spiceproxy | 17:10:54 |
