Red Hat Summit Red Hat SummitApoyoConsolaDesarrolladoresIniciar una pruebaContacto

Este contenido no está disponible en el idioma seleccionado.

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
Copiar enlace

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.

  1. Log in to the Administration Portal.

  2. Place the hosted engine node into Global Maintenance mode.

    1. Click Compute Hosts and select the hosted engine node.
    2. Click ⋮ Enable Global HA Maintenance.

  3. Shut down all virtual machines except the hosted engine virtual machine.

    1. Click Compute Virtual Machines.
    2. Select all virtual machines on hyperconverged hosts, except the hosted engine virtual machine.

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

  4. Shut down the hosted engine virtual machine.

    1. Log in to the hosted engine node.

    2. Run the following command on the hosted engine node to shut down the hosted engine virtual machine. 

      # hosted-engine --vm-shutdown
      Copy to Clipboard Toggle word wrap

  5. Shut down all hosts by running the following command on each host. 

    # shutdown -h now
    Copy to Clipboard Toggle word wrap

6.2. Starting up a hyperconverged cluster
Copiar enlace

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.

  1. Power on all hosts in the cluster.

  2. Ensure that the required services are available.

    1. Verify that the glusterd service 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
   [...]
      Copy to Clipboard Toggle word wrap

      If glusterd is not started, start it. 

      # systemctl start glusterd
      Copy to Clipboard Toggle word wrap

    2. Verify that host networks are available and hosts have IP addresses assigned to the required interfaces. 

      # ip addr show
      Copy to Clipboard Toggle word wrap

    3. Verify 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)
      Copy to Clipboard Toggle word wrap

    4. 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
      Copy to Clipboard Toggle word wrap

  3. Start the hosted engine virtual machine.

    1. Run the following command on the host that you want to be the hosted engine node. 

      # hosted-engine --vm-start
      Copy to Clipboard Toggle word wrap

    2. Verify that the hosted engine virtual machine has started correctly. 

      # hosted-engine --vm-status
      Copy to Clipboard Toggle word wrap

  4. Take the hosted engine virtual machine out of Global Maintenance mode.

    1. Log in to the Administration Portal.
    2. Click Compute Hosts and select the hosted engine node.
    3. Click ⋮ Disable Global HA Maintenance.

  5. Start any other virtual machines using Cockpit.

    1. Click Compute Virtualization.
    2. Select any virtual machines you want to start and click Run.
Volver arriba
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2025 Red Hat