Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1255126

Summary: [RFE] Gear migration between districts
Product: OpenShift Container Platform Reporter: Ricardo Martinelli de Oliveira <rmartine>
Component: RFEAssignee: Mike Barrett <mbarrett>
Status: CLOSED WONTFIX QA Contact: Johnny Liu <jialiu>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.2.0CC: erich, jokerman, libra-bugs, mbarrett, mmccomas
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-22 14:32:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ricardo Martinelli de Oliveira 2015-08-19 17:09:01 UTC 
Description of problem:
Customer wants to be able to migrate applications between districts when they want to change application gear size after noticing that applications are growing in number of requests and resources.

Version-Release number of selected component (if applicable):
2.2.x
Comment 2 Eric Rich 2015-09-11 16:48:24 UTC 
As it stands today you can move gears between 2 nodes in the same district [0]. The command (as shown below) already allows for what you are requesting (with the --destination_district_uuid and --change_district options) however it does so with limitations. 

    # oo-admin-move --help
    == Synopsis

    oo-admin-move: Move an app from one node to another

    == Usage

    oo-admin-move OPTIONS

    Options:
    --gear_uuid <gear_uuid>[,<gear_uuid>,<gear_uuid>]
        Gear uuid to move
    --destination_district_uuid <district_uuid>
        Destination district uuid
    -i|--target_server_identity <server_identity>
        Target server identity
    -p|--node_profile <node_profile>
        Node profile
    -t|--timeout
        timeout
    --json
        Print the move report at finish in JSON
    --change_district
        Move to a different district other than the source district
    -h|--help
        Show Usage info

The limitation here being that the GEAR UID can not exist in the new district to which you are moving it.