oVirt en 2 horas. Parte 4. Operaciones básicas

Contenido

• Crear una VM y plantilla ;
• Migración de VM (migración en vivo);
• Migración de almacenamiento (migración de almacenamiento);
• Renombrar VM y disco ;
• Actualizar oVirt-Host (hipervisor);
• Actualización de oVirt-Engine (gerente);
• Importar VM ;
• Gestión de tareas .

Artículos

1. Introducción
2. Instalación del gestor (ovirt-engine) e hipervisores (hosts)
3. Ajustes adicionales
4. Operaciones básicas: estamos aquí

• Portal de administración
• Portal de VM

status = unassigned or status = maintenance or status = installing or status = reboot or status = preparingformaintenance or status = pendingapproval or status = connecting or status = installingos or status = kdumping

Crear VM y plantilla

• unidad de rack - servidor;
• monitor - escritorio;
• 3 torres: servidor de la piscina;
• 3 monitores - escritorio de la piscina;
• rebobinar (rebobinar): sin estado (la máquina restablece su estado a su estado original después del apagado; todos los cambios se revierten);
• triángulo en el monitor naranja: el cambio de configuración solicitado requiere un reinicio.

Migración de VM (migración en vivo)

Migración de almacenamiento

Renombrar VM y disco

Actualizar oVirt-Host (hipervisor)

Actualizar oVirt-Engine (administrador)

1. Si es posible, haga un archivo o una instantánea de la máquina, asegúrese de que la última copia de seguridad programada se realizó correctamente.
2. Verificamos y actualizamos los paquetes de instalación:
   
   

   $ sudo engine-upgrade-check
   $ sudo update ovirt\*setup\*

3. La parte principal de la actualización la realiza el programa de configuración del motor. Ella hará una serie de preguntas de configuración, luego detendrá el servicio ovirt-engine, descargará e instalará paquetes actualizados, creará un archivo y actualizará la base de datos, aplicará la configuración actualizada e iniciará el servicio ovirt-engine.
   
   

   $ sudo engine-setup

   
   Tras una actualización exitosa, recibiremos el mensaje:
   
   

   Execution of setup completed successfully

   
   
   Ejemplo de salida del script de configuración del motor

   $ sudo engine-setup

   
   

   [ INFO  ] Stage: Initializing
   [ INFO  ] Stage: Environment setup
             Configuration files: ['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf', '/etc/ovirt-engine-setup.conf.d/10-packaging.conf', '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf']
             Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20200522232449-o97vyx.log
             Version: otopi-1.8.2 (otopi-1.8.2-1.el7)
   [ INFO  ] Stage: Environment packages setup
   [ INFO  ] Stage: Programs detection
   [ INFO  ] Stage: Environment setup (late)
   [ INFO  ] Stage: Environment customization
            
             --== PRODUCT OPTIONS ==--
            
            
             --== PACKAGES ==--
            
   [ INFO  ] Checking for product updates...
             Setup needs to install or update the following packages:
             [updated] ovirt-engine-4.3.5.5-1.el7.noarch will be updated
   ...
             [update] ovirt-engine-wildfly-overlay-17.0.1-1.el7.noarch is an update
             Replying "No" will abort Setup. You can pass the option "--offline" to prevent installing or updating packages.
             Do you wish to update them now? (Yes, No) [Yes]: 
   [ INFO  ] Checking for an update for Setup...
            
             --== NETWORK CONFIGURATION ==--
            
             Setup can automatically configure the firewall on this system.
             Note: automatic configuration of the firewall may overwrite current settings.
             NOTICE: iptables is deprecated and will be removed in future releases
             Do you want Setup to configure the firewall? (Yes, No) [Yes]: 
   [ INFO  ] firewalld will be configured as firewall manager.
            
             --== DATABASE CONFIGURATION ==--
            
             The detected DWH database size is 439 MB.
             Setup can backup the existing database. The time and space required for the database backup depend on its size. This process takes time, and in some cases (for instance, when the size is few GBs) may take several hours to complete.
             If you choose to not back up the database, and Setup later fails for some reason, it will not be able to restore the database and all DWH data will be lost.
             Would you like to backup the existing database before upgrading it? (Yes, No) [Yes]: 
             Perform full vacuum on the oVirt engine history
             database ovirt_engine_history@localhost?
             This operation may take a while depending on this setup health and the
             configuration of the db vacuum process.
             See https://www.postgresql.org/docs/10/sql-vacuum.html
             (Yes, No) [No]: 
            
             --== OVIRT ENGINE CONFIGURATION ==--
            
             Perform full vacuum on the engine database engine@localhost?
             This operation may take a while depending on this setup health and the
             configuration of the db vacuum process.
             See https://www.postgresql.org/docs/10/sql-vacuum.html
             (Yes, No) [No]: 
            
             --== STORAGE CONFIGURATION ==--
            
            
             --== PKI CONFIGURATION ==--
            
            
             --== APACHE CONFIGURATION ==--
            
            
             --== SYSTEM CONFIGURATION ==--
            
            
             --== MISC CONFIGURATION ==--
            
            
             --== END OF CONFIGURATION ==--
            
   [ INFO  ] Stage: Setup validation
             During execution engine service will be stopped (OK, Cancel) [OK]: 
   [ INFO  ] Cleaning stale zombie tasks and commands
            
             --== CONFIGURATION PREVIEW ==--
            
             Default SAN wipe after delete           : False
             Firewall manager                        : firewalld
             Update Firewall                         : True
             Host FQDN                               : ovirt.example.com
             Upgrade packages                        : True
             Set up Cinderlib integration            : False
             Engine database secured connection      : False
             Engine database user name               : engine
             Engine database name                    : engine
             Engine database host                    : localhost
             Engine database port                    : 5432
             Engine database host name validation    : False
             Engine installation                     : True
             PKI organization                        : JSC Open Lab
             Set up ovirt-provider-ovn               : False
             Configure WebSocket Proxy               : True
             DWH installation                        : True
             DWH database secured connection         : False
             DWH database host                       : localhost
             DWH database user name                  : ovirt_engine_history
             DWH database name                       : ovirt_engine_history
             Backup DWH database                     : True
             DWH database port                       : 5432
             DWH database host name validation       : False
             Configure Image I/O Proxy               : True
             Configure VMConsole Proxy               : True
            
             Please confirm installation settings (OK, Cancel) [OK]: 
   [ INFO  ] Cleaning async tasks and compensations
   [ INFO  ] Unlocking existing entities
   [ INFO  ] Checking the Engine database consistency
   [ INFO  ] Stage: Transaction setup
   [ INFO  ] Stopping engine service
   [ INFO  ] Stopping ovirt-fence-kdump-listener service
   [ INFO  ] Stopping dwh service
   [ INFO  ] Stopping Image I/O Proxy service
   [ INFO  ] Stopping vmconsole-proxy service
   [ INFO  ] Stopping websocket-proxy service
   [ INFO  ] Stage: Misc configuration (early)
   [ INFO  ] Stage: Package installation
   [ INFO  ] Yum Status: Downloading Packages
   ...
   [ INFO  ] Stage: Misc configuration
   [ INFO  ] Upgrading CA
   [ INFO  ] Not rewriting /etc/ovirt-imageio-proxy/ovirt-imageio-proxy.conf because it was changed manually. You might want to compare it with /etc/ovirt-imageio-proxy/ovirt-imageio-proxy.conf.new and edit as needed.
   [ INFO  ] Backing up database localhost:ovirt_engine_history to '/var/lib/ovirt-engine-dwh/backups/dwh-20200522233531.6LDItj.dump'.
   [ INFO  ] Creating/refreshing DWH database schema
   [ INFO  ] Configuring Image I/O Proxy
   [ INFO  ] Configuring WebSocket Proxy
   [ INFO  ] Backing up database localhost:engine to '/var/lib/ovirt-engine/backups/engine-20200522233538.LZCwME.dump'.
   [ INFO  ] Creating/refreshing Engine database schema
   [ INFO  ] Creating/refreshing Engine 'internal' domain database schema
             Unregistering existing client registration info.
   [ INFO  ] Generating post install configuration file '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf'
   [ INFO  ] Stage: Transaction commit
   [ INFO  ] Stage: Closing up
   [ INFO  ] Starting engine service
   [ INFO  ] Starting dwh service
   [ INFO  ] Restarting ovirt-vmconsole proxy service
            
             --== SUMMARY ==--
            
   [ INFO  ] Restarting httpd
             Web access is enabled at:
                 http://ovirt.example.com:80/ovirt-engine
                 https://ovirt.example.com:443/ovirt-engine
             SSH fingerprint: SHA256:JvilhbwRuMjBCJEjQVPlFQgk0aLaKz7Od0WzsZtx4j4
             Did not update /etc/ovirt-imageio-proxy/ovirt-imageio-proxy.conf because it was changed manually. You might want to compare it with /etc/ovirt-imageio-proxy/ovirt-imageio-proxy.conf.new and edit as needed.
            
             --== END OF SUMMARY ==--
            
   [ INFO  ] Stage: Clean up
             Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20200522232449-o97vyx.log
   [ INFO  ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20200522233608-setup.conf'
   [ INFO  ] Stage: Pre-termination
   [ INFO  ] Stage: Termination
   [ INFO  ] Execution of setup completed successfully

   
   
4. Actualizamos el sistema operativo y otros paquetes adicionales:
   

   $ sudo yum update

   
   Si es necesario (actualizando el núcleo o sus componentes) reiniciamos la máquina.

Importar VM

1. Importar VM desde VMware ESXi / VSPHERE se ejecuta en el host + autenticación al host donde se ejecuta ESXi / VSPHERE en
2. Importar KVM / Xen VM desde Libvirt: el usuario especifica la URL + autenticación al host donde se ejecuta Libvirt
3. Importar KVM / Xen VM desde una ruta determinada: el usuario especifica la ruta nfs / posix a la configuración y discos de la VM
4. Importar VM que se exportó desde VMware: el usuario especifica la ruta nfs / posix al archivo ova
5. Subir KVM / Xen VM: el usuario especifica los archivos de la configuración y los discos
6. Subir VM que se exportó desde VMware: el usuario especifica el archivo ova
7. Importar VM desde carpeta: el usuario especifica la ruta a la carpeta que contiene VM KVM / Xen o VM exportada desde VMware

Importar máquinas desde vCenter

• Fuente de datos: VMware;
• Proveedor externo: en Administración -> Proveedores puede configurar una plantilla para operaciones frecuentes;
• vCenter: nombre o dirección del servidor vCenter;
• ESXi: de qué hipervisor recogeremos el automóvil;
• Ceter de datos: ruta completa al clúster;
• Clúster: que contiene un clúster de hipervisor;
• Nombre de usuario / contraseña: nombre de usuario y contraseña para conectarse a vCenter;
• Verifique el certificado SSL del servidor: cuando use certificados autofirmados, deberá deshabilitar su verificación.

Importar máquinas de KVM

$ sudo vim /etc/sysconfig/libvirtd

LIBVIRTD_ARGS="--listen"

$ sudo cp /etc/libvirt/libvirtd.conf /etc/libvirt/libvirtd.conf.`date +%F`
$ sudo vim /etc/libvirt/libvirtd.conf

listen_tls = 0
listen_tcp = 1
listen_addr = "0.0.0.0"
auth_tcp = "none"

log_outputs="3:syslog:libvirtd"

$ sudo service libvirtd restart

$ sudo firewall-cmd --add-rich-rule='rule family="ipv4" source address="172.17.71.32/30" port port="16509" protocol="tcp" accept'

$ virsh -r -c 'qemu+tcp://mgmt@kvm46.example.com/system' list --all

Administración de tareas

[mgmt@ovirt-nodeNN] $ sudo vdsm-client Host getAllTasksInfo
[mgmt@ovirt-nodeNN] $ sudo vdsm-client Task getStatus taskID=<TASKID>
[mgmt@ovirt-nodeNN] $ sudo vdsm-client Task stop taskID=<TaskID>
[mgmt@ovirt-nodeNN] $ sudo vdsm-client Task clear taskID=<TaskID>
[mgmt@ovirt-nodeNN] $ sudo vdsm-client Host getAllTasksInfo

$ sudo vdsm-client Task -h

[mgmt@ovirt-engine] $ sudo /usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh --help

[mgmt@ovirt-engine] $ sudo scl enable rh-postgresql10 "psql -d engine -U postgres"

su postgres
psql -d engine -U postgres
select * from job order by start_time desc;

select DeleteJob('UUID_HERE');

select DeleteJob('ed0127c7-b052-4ec2-a67c-8b3a65d55e19');