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
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.