Bug #3817
migrating vm's to a different cluster
Status: | Closed | Start date: | 05/23/2015 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | - | |||
Target version: | - | |||
Resolution: | worksforme | Pull request: | ||
Affected Versions: | OpenNebula 4.10 |
Description
- [VirtualMachineMigrate] Cannot migrate to a different cluster.
- VM running in a host in cluster [100]
- New host is in cluster [101]
--> Migration was from [100] to [101] was not possible
History
#1 Updated by Ruben S. Montero about 6 years ago
- Status changed from Pending to Closed
- Resolution set to worksforme
This is the expected behavior. Groups of physical resources that work together should be in the same cluster. Then you can adjust access by creating subsets of it in the form of VDCs.
#2 Updated by Nico Schottelius about 6 years ago
Ruben,
is it possible to migrate a VM to a different host with a different network using VDCs? If so, can you shortly give a pointer on how that is possible?