New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFE: usecase: automatically clone new virtual machine #915
Comments
@jscotka In general regarding contributing see Here my current personal offhanded opinion regarding I do not like such ISOs because I think I would prefer that an explicit confirmation action is needed I mean not something like "rear mkrescue autorecover" I mean some confirmation at ISO boot time, i.e. something But I don't know if one can provide such kind of For example if one could simulate some keyboard input But this is only some offhanded thoughts because |
A totally different idea: A "rear recover" on a "new virtual machine" means Accordingly a full automated "rear recover" might be This could make those possibly descructive ISOs |
I agree with your views, yep, it can be destructive, but I know what I'm doing and in case I add some option like "rear mkbackup --autorecover" or whatever, it should accept my will, that I know what I'm doing. |
Only FYI regarding "detect that disc is empty": I think there could be a relation to #799 When such a "cleanupdisk" script does not find In short: |
@jscotka to autostart the ISO you can define in |
My plan for the "cleanupdisk" script is that it is run Perhaps after rear 1.19 was released I should implement I assume such a "cleanupdisk" script cannot cause any harm In the end the goal of such a "cleanupdisk" script is Because "rear recover" must work at least on a |
I'm not sure if it should only work on disc of same type and size. From my POV It would work on any empty HDD size and type are more less irrelevant, or better to say size is important, but size could be same or bigger, but I prefer to autostart recovering without any asking on any type and size. |
I think when the target disks (i.e. those disks |
@jscotka @jsmeix Will check it out within the rear-automated-testing (https://github.com/gdha/rear-automated-testing) project. Currently using PXE, but ISO is in scope as well (but not yet fully implemented). Need some more time. |
@jscotka @jsmeix PXE and ISO can now do an unattended recovery - see as example the config file https://github.com/gdha/rear-automated-testing/blob/master/templates/ISO-booting-with-NETFS-NFS.conf |
@jscotka @gdha But this does not mean that "rear recover" can For example when the disk size is different Also when the network interface has changed there Running "rear recover" fully unattended |
@jscotka Is your question sufficient answered? |
Hi,
I've tested rear and I wanted to use rear for cloning one virt machine to anither one:
cat /etc/rear/local.conf
OUTPUT=ISO
OUTPUT_URL="file:///issoo.iso"
BACKUP=NETFS
BACKUP_URL="iso:///bbbb/"
then using virt-install like:
virt-install -r 2048 -n newrear -f new.img --cdrom rear-rearclient.iso
it is working moreless perfect, but it needs to click in boot menu that I want automatical recovery, and then click 1 that I want to use disc /dev/sda and then 5 to allow resizing of partitions.
I would suggest to have there some option for command rear -v mkbackup
what creates ISO what will be tolerant and fully automated (something like kickstart for installation), no asking, just boot from iso and recover and config first possible disc (in most cases there is one disc, so it could be acceptable)
like: option --force
Regards
Honza
The text was updated successfully, but these errors were encountered: