To my knowledge, no export/import process exists from SmartOS to Triton. I have, however used a combination of provisioning and rsync to migrate systems into Trition. In my case, this was from SDC 6 to Triton, but the process should be identical for you assuming you are only using zone datasets. None of my users reported issues although I’m certain this is about as far from a supported solution as it gets. Also note that I have not tested this with LX-Zones.
Your source will be the zone's ZFS volume on your SmartOS server and your Destination will be the zone’s ZFS volume on compute node where Triton provisioned it. Writ large, you are provisioning a new VM on Triton with the exact same dataset AND IP address as the VM on your SmartOS server that you wish to migrate. You then use rsync to send over everything from the source volume to the destination volume. Triton will now now know about the VM and you should have only the diffs from the source VM. It’s pretty guerrilla, but it did work for me. Worst case, you still have the SmartOS zone in its original configuration and can go back to that if things go sideways. I hope this helps. Cliff > On Sep 5, 2017, at 8:57 AM, John Barfield <[email protected]> wrote: > > Greetings, > > I’ve been running a Vanilla SmartOS environment for a couple of years > manually building VM’s and managing the nodes as virtualization hosts with > vmadm, ZFS, json, etc. > > I’ve now built out a triton datacenter deployment separately in the same > datacenter. > > Is it possible, and if it is, would there be a document in existence > outlining the process, to simply reboot a SmartOS node with the Triton CN usb > ipxe key and import existing VM’s, Zones, and so forth from the zones pool? > > And secondarily, if the first question is not possible, could someone send a > process for simply moving (v2v) VM’s from SmartOS nodes into the triton cloud? > > One could only assume that at the very least all of the VM’s would need to > follow the same triton package guidelines and the network configurations > would need to be identical. > > I’m looking for an easier way, than simply provisioning and migrating every > single VM manually with vmadm or zfs send/receive processes. > > Thanks! > > John Barfield > Engineering and Stuff > > M: +1 (214) 425-0783 O: +1 (214) 506-8354 > [email protected] <mailto:[email protected]> > > <image001.png> > 4925 Greenville Ave, Ste 900 > Dallas, TX 75206 > > For Support Requests: > http://support.bissinc.com <http://support.bissinc.com/> or > [email protected] <mailto:[email protected]> > > Follow us on Twitter for Network Status & Updates! > > <image002.gif> <https://twitter.com/johnbarfield> > smartos-discuss | Archives > <https://www.listbox.com/member/archive/184463/=now> > <https://www.listbox.com/member/archive/rss/184463/26908954-1558d6be> | > Modify <https://www.listbox.com/member/?&;> Your Subscription > <http://www.listbox.com/> ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
