[ X-post to ganeti and ganeti-devel mailing lists. ]
Hi all, Ganeti is now used in our compagny, internally. We'd like to make it full solution ready for our customers but we are missing some critical features. Before going further and starting to play with the code I'd like to share my thoughts for comments. The idea is to submit patches in the correct direction as early as possible in the development process. I didn't looked much at the code, yet. 1. Improving the KVM integration. 1.1. Hibernation. AFAICT, we can't hibernate a KVM instance from Ganeti. I guess it is possible to do with QMP and store the RAM in a dedicated path or LVM volume. 1.2. CPU Tunning. - CPU pinning (mask) is supported. - CPU SMP is under work. 2. Snapshots. The current gnt-backup tool does not fit our needs. Here are some limitations I've found (correct me if I'm wrong): - It relies on os-type (and variants?) which is fine if you have homogeneous instances but does not help for a lot of per-instance customing. BTW, os-interface mix various kind of requirements (creation, export/import, rename, verify). It is hard for us to get relevant families of instances matching all these kind of requirements. - gnt-backup command does not support more than one export strategy. - The export scripts are too much hard do understand and modify for our system administrators. But full instances management must be accessible for sysadmins (creation, tunning, backups, etc). - Perhaps other limitations I'm not aware? I believe it might worth starting another tool from scratch with a new design. I'm not saying it would have to replace the current gnt-backup. I'm more suggesting something like 'gnt-snapshot' or whatever at the side. Any thoughts on this? 3. Clone. Clonning an instance looks not supported. 4. Different disk types for an instance. I've heard some discussions about that but can't remember what's the current status. Not urgent at all but I guess this is something we will need some day. Regards, -- Nicolas Sebrecht
