Show Table of Contents
6.3.5. Moving Gears Between Nodes
The
oo-admin-move command moves a gear from one node to another. Note that moving gears requires a rsync_id_rsa private key in the broker host's /etc/openshift/ directory and a matching public key in each node host's /root/.ssh/authorized_keys file as explained in the OpenShift Enterprise Deployment Guide at https://access.redhat.com/site/documentation.
A gear retains its UID when moved, therefore cross-district moves are only allowed when the destination district has the same gear UID available.
Run the
oo-admin-move command on the broker host to move a gear from one node to another:
Example 6.7. Moving a Gear from One Node to Another
# oo-admin-move --gear_uuid 3baf79139b0b449d90303464dfa8dd6f -i node2.example.com
URL: http://app3-username.example.com
Login: username
App UUID: 3baf79139b0b449d90303464dfa8dd6f
Gear UUID: 3baf79139b0b449d90303464dfa8dd6f
DEBUG: Source district uuid: NONE
DEBUG: Destination district uuid: NONE
[...]
DEBUG: Starting cartridge 'ruby-1.8' in 'app3' after move on node2.example.com
DEBUG: Fixing DNS and mongo for gear 'app3' after move
DEBUG: Changing server identity of 'app3' from 'node1.example.com' to 'node2.example.com'
DEBUG: The gear's node profile changed from medium to small
DEBUG: Deconfiguring old app 'app3' on node1.example.com after move
Successfully moved 'app3' with gear uuid '3baf79139b0b449d90303464dfa8dd6f' from 'node1.example.com' to 'node2.example.com'
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.