On 10/27/2011 03:55 AM, Daniel P. Berrange wrote:
From: "Daniel P. Berrange"<berrange@xxxxxxxxxx>
This adds a page documenting many aspects of migration:
- The types of migration (managed direct, p2p, unmanaged direct)
- Data transports (native, tunnelled)
- Migration URIs
- Config file handling
- Example scenarios
In v2:
- All Eric's fixes
- Squash in the preceeding patch which was mistakenly
left out before
Thanks for the cleanup.
ACK with nits:
+<h3><a id="scenarionativepeer2peer">Native migration, client to and peer2peer between, two libvirtd servers</a></h3>
+
+<p>
+ virDomainMigrate, with the VIR_MIGRATE_PEER2PEER flag set,
+ using the libvirt URI format for the 'uri' parameter. The
+ destination libvirtd server will automatically determine
+ the native hypervisor URI for migration, based off the
+ primary hostname. The optional uri parameter controls how
+ the source libvirtd connects to the destination libvirtd,
+ in case it is not accessible using the same address that
+ the client uses to connect to the destiation, or a different
s/destiation/destination/
+<h3><a id="scenariotunnelpeer2peer1">Tunnelled migration, client and peer2peer between two libvirtd servers</a></h3>
+
+<p>
+ virDomainMigrate, with the VIR_MIGRATE_PEER2PEER& VIR_MIGRATE_TUNNELLED
+ flags set, using the libvirt URI format for the 'uri' parameter. The
+ destination libvirtd server will automatically determine
+ the native hypervisor URI for migration, based off the
+ primary hostname. The optional uri parameter controls how
+ the source libvirtd connects to the destination libvirtd,
+ in case it is not accessible using the same address that
+ the client uses to connect to the destiation, or a different
s/destiation/destination/
--
Eric Blake eblake@xxxxxxxxxx +1-801-349-2682
Libvirt virtualization library http://libvirt.org
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list