Bug 1420575

Summary: [Docs][RFE][Admin] Document the ability to change an initialized Data Center type to Shared or Local
Product: Red Hat Enterprise Virtualization Manager Reporter: Byron Gravenorst <bgraveno>
Component: DocumentationAssignee: Avital Pinnick <apinnick>
Status: CLOSED CURRENTRELEASE QA Contact: Byron Gravenorst <bgraveno>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 4.1.0CC: lbopf, lsurette, rbalakri, srevivo, ykaul, ylavi
Target Milestone: ovirt-4.1.3Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-22 06:52:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Docs RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1302185    
Bug Blocks:    

Description Byron Gravenorst 2017-02-09 01:12:23 UTC
Users can now change an initialized Data Center type to Shared or Local. The following updates will be available: 

1. Shared to Local - Only for a Data Center that does not contain more than one host and more than one cluster, since a local Data Center does not support it. The Manager will validate and block this operation with the following messages:

    CLUSTER_CANNOT_ADD_MORE_THEN_ONE_HOST_TO_LOCAL_STORAGE
    VDS_CANNOT_ADD_MORE_THEN_ONE_HOST_TO_LOCAL_STORAGE

2. Local to Shared - Only for a Data Center that does not contain a local Storage Domain. The Manager will validate and block this operation with the following message:

    ERROR_CANNOT_CHANGE_STORAGE_POOL_TYPE_WITH_LOCAL.

This update is useful for data domains that are used to move virtual machines or templates around.

Comment 1 Lucy Bopf 2017-08-04 02:07:54 UTC
Assigning to Avital for review.

Avital, I don't think we need to go as far as adding the error messages, but a short explanation of the allowed updates would be good. I suspect there are also places in the docs set where we say that such updates are not allowed, so those will need to be removed if they exist.