Questo contenuto non è disponibile nella lingua selezionata.
Chapter 6. Basic Operations
Some basic operations are required for many administrative and troubleshooting tasks. This section covers how to safely perform basic tasks like shutting down and starting up the hyperconverged cluster.
6.1. Shutting down a hyperconverged cluster Copia collegamentoCollegamento copiato negli appunti!
Shutting down a hyperconverged cluster is more complex than shutting down a traditional compute or storage cluster. Follow these instructions to shut down your hyperconverged cluster safely.
- Log in to the Administration Portal.
Place the hosted engine node into Global Maintenance mode.
-
Click Compute
Hosts and select the hosted engine node. -
Click ⋮
Enable Global HA Maintenance.
-
Click Compute
Shut down all virtual machines except the hosted engine virtual machine.
-
Click Compute
Virtual Machines. - Select all virtual machines on hyperconverged hosts, except the hosted engine virtual machine.
Click Shut Down. This shuts the virtual machine down gracefully.
If your virtual machine is not responding, click the dropdown arrow beside Shut Down and click Force Shut Down instead.
-
Click Compute
Shut down the hosted engine virtual machine.
- Log in to the hosted engine node.
Run the following command on the hosted engine node to shut down the hosted engine virtual machine.
# hosted-engine --vm-shutdown
Shut down all hosts by running the following command on each host.
# shutdown -h now
6.2. Starting up a hyperconverged cluster Copia collegamentoCollegamento copiato negli appunti!
Starting up a hyperconverged cluster is more complex than starting up a traditional compute or storage cluster. Follow these instructions to start up your hyperconverged cluster safely.
- Power on all hosts in the cluster.
Ensure that the required services are available.
Verify that the
glusterdservice started correctly on all hosts.# systemctl status glusterd ● glusterd.service - GlusterFS, a clustered file-system server Loaded: loaded (/usr/lib/systemd/system/glusterd.service; enabled; vendor preset: disabled) Drop-In: /etc/systemd/system/glusterd.service.d └─99-cpu.conf Active: active (running) since Wed 2018-07-18 11:15:03 IST; 3min 48s ago [...]If glusterd is not started, start it.
# systemctl start glusterdVerify that host networks are available and hosts have IP addresses assigned to the required interfaces.
# ip addr showVerify that all hosts are part of the storage cluster (listed as Peer in Cluster (Connected)).
# gluster peer status Number of Peers: 2 Hostname: 10.70.37.101 Uuid: 773f1140-68f7-4861-a996-b1ba97586257 State: Peer in Cluster (Connected) Hostname: 10.70.37.102 Uuid: fc4e7339-9a09-4a44-aa91-64dde2fe8d15 State: Peer in Cluster (Connected)Verify that all bricks are shown as online.
# gluster volume status engine Status of volume: engine Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick 10.70.37.28:/gluster_bricks/engine/en gine 49153 0 Y 23160 Brick 10.70.37.29:/gluster_bricks/engine/en gine 49160 0 Y 12392 Brick 10.70.37.30:/gluster_bricks/engine/en gine 49157 0 Y 15200 Self-heal Daemon on localhost N/A N/A Y 23008 Self-heal Daemon on 10.70.37.30 N/A N/A Y 10905 Self-heal Daemon on 10.70.37.29 N/A N/A Y 13568 Task Status of Volume engine ------------------------------------------------------------------------------ There are no active volume tasks
Start the hosted engine virtual machine.
Run the following command on the host that you want to be the hosted engine node.
# hosted-engine --vm-startVerify that the hosted engine virtual machine has started correctly.
# hosted-engine --vm-status
Take the hosted engine virtual machine out of Global Maintenance mode.
- Log in to the Administration Portal.
-
Click Compute
Hosts and select the hosted engine node. -
Click ⋮
Disable Global HA Maintenance.
Start any other virtual machines using Cockpit.
-
Click Compute
Virtualization. - Select any virtual machines you want to start and click Run.
-
Click Compute