Hi, I realize there's work ongoing for this particular feature in 3.0, and I'm eager to play with developer releases in the coming weeks. For now though, how does one generate a "persistent" vm, such that I can resubmit the same template file for a specific vm and have it pick up where it left off, disks with data and everything?
Assuming I'm using the NFS transfer manager, it seems like I should - manually add a disk into the image repository for that vm - set the disk image to be persistent - set the vm template to use the specific disk image I just added - set clone=no in the vm template file for the disk - set context script for vm to pick up the correct ip, hostname, etc.. - keep the template description around so that I may "onevm create" it as needed Is that correct? I'm sorry if this is an asked an answered question, but when googling I see the asked part but have yet to find an "answered" post. This may be because I am new to OpenNebula and lack the correct vocabulary to fine tune my searches. Thanks, -n -- ------------------------------------------- nathan hruby <nhr...@gmail.com> metaphysically wrinkle-free ------------------------------------------- _______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org