Description of problem: Currently, a DC's local/shared property can't be changed. Bug 1302185 breaks down some of the distinction and allows attaching shared domains to local DCs. The next step is the ability to convert a local DC to a shared one (and vice versa, although it's a less interesting usecase). Prerequisite to convert a DC from local to shared: The storage pool has no local domains in it (regardless of the status). Prerequisite to convert a DC from shared to local: The storage pool has no shared domains (i.e., no domains at all - regardless of status) and no more than one cluster which contains no more than one domain. Version-Release number of selected component (if applicable): 3.6.0 How reproducible: 100%
The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.
(In reply to Allon Mureinik from comment #0) > Description of problem: > Currently, a DC's local/shared property can't be changed. Bug 1302185 breaks > down some of the distinction and allows attaching shared domains to local > DCs. > The next step is the ability to convert a local DC to a shared one (and vice > versa, although it's a less interesting usecase). > > Prerequisite to convert a DC from local to shared: The storage pool has no > local domains in it (regardless of the status). > > Prerequisite to convert a DC from shared to local: The storage pool has no > shared domains (i.e., no domains at all - regardless of status) and no more > than one cluster which contains no more than one domain. We currently support this kind of update already. Is there a reason to block this for a local DC updated to shared even if it contains more than one shared SD.
-------------------------------------- Tested with the following code: ---------------------------------------- vdsm-4.18.999-1138.git6c51957.el7.centos.x86_64 ovirt-engine-4.1.0-0.2.master.20161203231307.gitd7d920b.el7.centos.noarch Tested with the following scenario: Steps to Reproduce: 1. create new local dc with one host and few shared storage domains 2. edit the dc and change the storage type from local to shared 3. edit again the dc and change the storage type from shared to local Actual results: dc type is being updated to the right storage type Expected results: Moving to VERIFIED! Additional info: This was tested with active shared storage domains when updated from local to shared, though Allons' prerequisites mention no storage domains at all: Prerequisite to convert a DC from shared to local: The storage pool has no shared domains (i.e., no domains at all - regardless of status) This is still on NEED INFO
(In reply to Maor from comment #2) > (In reply to Allon Mureinik from comment #0) > > Description of problem: > > Currently, a DC's local/shared property can't be changed. Bug 1302185 breaks > > down some of the distinction and allows attaching shared domains to local > > DCs. > > The next step is the ability to convert a local DC to a shared one (and vice > > versa, although it's a less interesting usecase). > > > > Prerequisite to convert a DC from local to shared: The storage pool has no > > local domains in it (regardless of the status). > > > > Prerequisite to convert a DC from shared to local: The storage pool has no > > shared domains (i.e., no domains at all - regardless of status) and no more > > than one cluster which contains no more than one domain. > > We currently support this kind of update already. > Is there a reason to block this for a local DC updated to shared even if it > contains more than one shared SD. You are correct, this is definitely a mistake. Shared domains shouldn't block changing a DC from local to shared. The only prerequisite should be "no more than one CLUSTER which contains no more than one HOST".