- Users - oVirt List Archives

IoT Big Data design on AWS
by Soujanya Bargavi 05 Jan '19

05 Jan '19

I'm trying to design a big IoT solution of millions of devices starting from zero. That's why I need a highly scalable platform like AWS. My devices are going to report data using AWS IoT, and that's the only thing I've really decided. I need to store a lot of data like a temperature measure every 15 minutes on each device so for that measures I've planned to insert those measures directly to DynamoDB using IoT Rules, but on the other side, I need a relational structure to store companies, temperature sensors, etc. So I thought I could store that in MySQL RDS. After that, I need to configure a proper analysis tool, so I was thinking of Kinesis and load the data from Redshift after ETL using Data Pipeline since AWS https://goo.gl/n2qNUi Glue doesn't support DynamoDB. I'm new with some of the services so I don't know exactly what I'm doing and I don't know if this approach is the best one. What do you think?.

1 0

Ovirt Engine UI bug- cannot attache networks to hosts
by Leo David 05 Jan '19

05 Jan '19

Hi Everyone, Using self hosted-engine 4.2.7.5-1.el7 running on ovirt-node 4.2.7, i am trying to attache hosts to a newlly created network for gluster/migration traffic. Oncei click on Networks->gluster-Hosts- Unattached, i get the following error: Uncaught exception occurred. Please try reloading the page. Details: (TypeError) : M9(...) is null Please have your administrator check the UI logs So to make the cluster installation possible, i had to use ovirt 4.2.2 and manually install ovirt-engine-appliance-4.2-20180626.1.el7 on the nodes before deploying self-hosted engine ( version that has other problems, like not being able to get dasboards in cloudforms/manageiq - ovirt-engine-dwh is missing ). Is it possible to: 1. upgrade actual hosted-engine version to the latest that has this module properly installed ? 2. fix the latest ( upgraded ) version so i can attach hosts to networks ? Thank you very much ! Leo -- Best regards, Leo David

6 14

oVirt Storage questions
by michael＠wanderingmad.com 04 Jan '19

04 Jan '19

From previous thread about gluster issues, things seem to be running much better than before, and it has raised a few questions that I can't seem to find any answers to: Setup: 3 hyperconverged nodes each node has 1x 1tb SSD and 1x 500gb nVME drive each node is connected via ethernet and also by a 40gb infiniband connection for the gluster replication. Questions: 1. I created a 3tb VDO drive on the SSD and a 1.3tb VDO Drive on the nVME drive with a 1Gb cache on each server and I enabled the RDMA transport.

1 0

migration failed
by 董青龙 04 Jan '19

04 Jan '19

Hi all, I have an ovirt4.2 environment of 3 hosts. Now all vms in this environment could not be migrated. But all the vms could be started on all 3 hosts. Anyone can help? Thanks a lot! engine logs: 2019-01-02 09:41:26,868+08 INFO [org.ovirt.engine.core.bll.MigrateVmCommand] (default task-9) [3eed5f0e-aaf5-4dce-bf30-2c49e09ab30d] Lock Acquired to object 'EngineLock:{exclusiveLocks='[eff7f697-8a07-46e5-a631-a1011a0eb836=VM]', sharedLocks=''}' 2019-01-02 09:41:26,978+08 INFO [org.ovirt.engine.core.bll.MigrateVmCommand] (EE-ManagedThreadFactory-engine-Thread-168938) [3eed5f0e-aaf5-4dce-bf30-2c49e09ab30d] Running command: MigrateVmCommand internal: false. Entities affected : ID: eff7f697-8a07-46e5-a631-a1011a0eb836 Type: VMAction group MIGRATE_VM with role type USER 2019-01-02 09:41:27,019+08 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (EE-ManagedThreadFactory-engine-Thread-168938) [3eed5f0e-aaf5-4dce-bf30-2c49e09ab30d] START, MigrateVDSCommand( MigrateVDSCommandParameters:{hostId='0aff0075-4b41-4f37-98de-7433a17cd47e', vmId='eff7f697-8a07-46e5-a631-a1011a0eb836', srcHost='horeb66', dstVdsId='5bb18f6e-9c7e-4afd-92de-f6482bf752e5', dstHost='horeb65:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompressed='false', consoleAddress='null', maxBandwidth='500', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, params=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, {limit=-1, action={name=abort, params=[]}}]]', dstQemu='192.168.128.78'}), log id: 1bd72db2 2019-01-02 09:41:27,019+08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-168938) [3eed5f0e-aaf5-4dce-bf30-2c49e09ab30d] START, MigrateBrokerVDSCommand(HostName = horeb66, MigrateVDSCommandParameters:{hostId='0aff0075-4b41-4f37-98de-7433a17cd47e', vmId='eff7f697-8a07-46e5-a631-a1011a0eb836', srcHost='horeb66', dstVdsId='5bb18f6e-9c7e-4afd-92de-f6482bf752e5', dstHost='horeb65:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompressed='false', consoleAddress='null', maxBandwidth='500', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, params=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, {limit=-1, action={name=abort, params=[]}}]]', dstQemu='192.168.128.78'}), log id: 380b8d38 2019-01-02 09:41:27,025+08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-168938) [3eed5f0e-aaf5-4dce-bf30-2c49e09ab30d] FINISH, MigrateBrokerVDSCommand, log id: 380b8d38 2019-01-02 09:41:27,029+08 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (EE-ManagedThreadFactory-engine-Thread-168938) [3eed5f0e-aaf5-4dce-bf30-2c49e09ab30d] FINISH, MigrateVDSCommand, return: MigratingFrom, log id: 1bd72db2 2019-01-02 09:41:27,036+08 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-168938) [3eed5f0e-aaf5-4dce-bf30-2c49e09ab30d] EVENT_ID: VM_MIGRATION_START(62), Migration started (VM: win7, Source: horeb66, Destination: horeb65, User: admin@internal-authz). 2019-01-02 09:41:41,557+08 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-30) [] VM 'eff7f697-8a07-46e5-a631-a1011a0eb836'(win7) moved from 'MigratingFrom' --> 'Up' 2019-01-02 09:41:41,557+08 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-30) [] Adding VM 'eff7f697-8a07-46e5-a631-a1011a0eb836'(win7) to re-run list 2019-01-02 09:41:41,567+08 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-30) [] Rerun VM 'eff7f697-8a07-46e5-a631-a1011a0eb836'. Called from VDS 'horeb66' 2019-01-02 09:41:41,570+08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-168945) [] START, MigrateStatusVDSCommand(HostName = horeb66, MigrateStatusVDSCommandParameters:{hostId='0aff0075-4b41-4f37-98de-7433a17cd47e', vmId='eff7f697-8a07-46e5-a631-a1011a0eb836'}), log id: 4ed2923c 2019-01-02 09:41:41,573+08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-168945) [] FINISH, MigrateStatusVDSCommand, log id: 4ed2923c 2019-01-02 09:41:41,583+08 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-168945) [] EVENT_ID: VM_MIGRATION_TRYING_RERUN(128), Failed to migrate VM win7 to Host horeb65 . Trying to migrate to another Host. 2019-01-02 09:41:41,642+08 INFO [org.ovirt.engine.core.bll.MigrateVmCommand] (EE-ManagedThreadFactory-engine-Thread-168945) [] Running command: MigrateVmCommand internal: false. Entities affected : ID: eff7f697-8a07-46e5-a631-a1011a0eb836 Type: VMAction group MIGRATE_VM with role type USER 2019-01-02 09:41:41,671+08 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (EE-ManagedThreadFactory-engine-Thread-168945) [] START, MigrateVDSCommand( MigrateVDSCommandParameters:{hostId='0aff0075-4b41-4f37-98de-7433a17cd47e', vmId='eff7f697-8a07-46e5-a631-a1011a0eb836', srcHost='horeb66', dstVdsId='20786f47-87fe-4ef6-be82-b580e5d0a350', dstHost='horeb67:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompressed='false', consoleAddress='null', maxBandwidth='500', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, params=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, {limit=-1, action={name=abort, params=[]}}]]', dstQemu='192.168.128.76'}), log id: 4611863 2019-01-02 09:41:41,672+08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-168945) [] START, MigrateBrokerVDSCommand(HostName = horeb66, MigrateVDSCommandParameters:{hostId='0aff0075-4b41-4f37-98de-7433a17cd47e', vmId='eff7f697-8a07-46e5-a631-a1011a0eb836', srcHost='horeb66', dstVdsId='20786f47-87fe-4ef6-be82-b580e5d0a350', dstHost='horeb67:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompressed='false', consoleAddress='null', maxBandwidth='500', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, params=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, {limit=-1, action={name=abort, params=[]}}]]', dstQemu='192.168.128.76'}), log id: 7d20b357 2019-01-02 09:41:41,677+08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (EE-ManagedThreadFactory-engine-Thread-168945) [] FINISH, MigrateBrokerVDSCommand, log id: 7d20b357 2019-01-02 09:41:41,682+08 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (EE-ManagedThreadFactory-engine-Thread-168945) [] FINISH, MigrateVDSCommand, return: MigratingFrom, log id: 4611863 2019-01-02 09:41:41,686+08 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-168945) [] EVENT_ID: VM_MIGRATION_START(62), Migration started (VM: win7, Source: horeb66, Destination: horeb67, User: admin@internal-authz). 2019-01-02 09:41:56,575+08 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-45) [] VM 'eff7f697-8a07-46e5-a631-a1011a0eb836'(win7) moved from 'MigratingFrom' --> 'Up' 2019-01-02 09:41:56,575+08 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-45) [] Adding VM 'eff7f697-8a07-46e5-a631-a1011a0eb836'(win7) to re-run list 2019-01-02 09:41:56,584+08 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-45) [] Rerun VM 'eff7f697-8a07-46e5-a631-a1011a0eb836'. Called from VDS 'horeb66' 2019-01-02 09:41:56,625+08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-168952) [] START, MigrateStatusVDSCommand(HostName = horeb66, MigrateStatusVDSCommandParameters:{hostId='0aff0075-4b41-4f37-98de-7433a17cd47e', vmId='eff7f697-8a07-46e5-a631-a1011a0eb836'}), log id: 4ded4ce9 2019-01-02 09:41:56,628+08 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-168952) [] FINISH, MigrateStatusVDSCommand, log id: 4ded4ce9 2019-01-02 09:41:56,638+08 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-168952) [] EVENT_ID: VM_MIGRATION_TRYING_RERUN(128), Failed to migrate VM win7 to Host horeb67 . Trying to migrate to another Host. 2019-01-02 09:41:56,695+08 WARN [org.ovirt.engine.core.bll.MigrateVmCommand] (EE-ManagedThreadFactory-engine-Thread-168952) [] Validation of action 'MigrateVm' failed for user admin@internal-authz. Reasons: VAR__ACTION__MIGRATE,VAR__TYPE__VM,VAR__ACTION__MIGRATE,VAR__TYPE__VM,VAR__ACTION__MIGRATE,VAR__TYPE__VM,VAR__ACTION__MIGRATE,VAR__TYPE__VM,SCHEDULING_NO_HOSTS 2019-01-02 09:41:56,696+08 INFO [org.ovirt.engine.core.bll.MigrateVmCommand] (EE-ManagedThreadFactory-engine-Thread-168952) [] Lock freed to object 'EngineLock:{exclusiveLocks='[eff7f697-8a07-46e5-a631-a1011a0eb836=VM]', sharedLocks=''}' 2019-01-02 09:41:56,706+08 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-168952) [] EVENT_ID: VM_MIGRATION_NO_VDS_TO_MIGRATE_TO(166), No available host was found to migrate VM win7 to. 2019-01-02 09:41:56,709+08 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-168952) [] EVENT_ID: VM_MIGRATION_FAILED(65), Migration failed (VM: win7, Source: horeb66).

2 4

Which option is best for storage?
by geoff＠pdclouds.com.au 04 Jan '19

04 Jan '19

Hi, Which is the preferred option for connecting oVirt VM farm to SAN/NAS? NFS (10G), iSCSI (10G) or FC (8G)? We are confused, some people say iSCSI is preferred and others say NFS performs the better than iSCSI, but FC is most expensive but performs the best overall.... Would value expert opinion. Cheers Geoff

3 2

Unable to increase memory or CPU on hosted Engine version 4.2.5.2
by Florian Schmid 04 Jan '19

04 Jan '19

Hi, I'm using version 4.2.5.2 and every article I found, I read that with oVirt 4.2, it should be possible to update CPU and memory for hosted Engine in UI. Now, when I'm trying to do this, even being on global maintenance, I always get the same error: Error while executing action: HostedEngine: There was an attempt to change Hosted Engine VM values that are locked. My problem is, that I need to increase the memory, because we had now several times in the last 2 or 3 months an out of memory kill of the java process. What is the best way to increase memory here? Should I do it over the config file? But how is then the OVF updated? BR Florian

2 3

Replacing Export Domain by Data Domain
by tehnic＠take3.ro 03 Jan '19

03 Jan '19

Hello all, because using an export domain is deprecated i deleted my export domain and use now a data domain instead. I used the export domain for complete image backups of my production virtual machines. By using now a data domain its even more comfortable because i can clone a snapshot directly on my backup data domain. But there is a (small?) inconvenience: I cannot "unregister" the cloned snapshot and i dont want to see them all the time in the "Virtual Machines" list. For the moment i use a bookmark in the "Vms:" filter. After detaching the domain the VMs are away, reattaching brings them back for possible "Import VM". Is there a possibility to set the cloned VM directly to this "unregistered" state without detaching and reattaching the complete domain? Best regards, Robert

1 0

Information about un-imported VMs. Delete Request.
by Jacob Green 03 Jan '19

03 Jan '19

I have a Fiber Channel domain, it works, there are some VMs in the VM import tab of the domain that I want to remove, I cannot import them, because they technically already exsist with a duplicate VMID. Is there a way to do this? Alternatively if I cannot delete the data related the the imports, I want to remove the disks attached to these un-imported VM's to free up space on my Fiber Channel, is there a way to reliably identify which LVM id's belong to those un-imported VMs? Thank you. -- Jacob Green Systems Admin American Alloy Steel 713-300-5690

1 0

Re: Problem with SAN FC and Ovirt 4.2
by Arsène Gschwind 03 Jan '19

03 Jan '19

could you share the output of both command? On Thu, 2019-01-03 at 07:02 -0300, Sebastian Antunez N. wrote: Hello I see with multipath -ll and lsbls but not show the LUN Regards Sebas El jue., 3 ene. 2019 a las 3:57, Arsène Gschwind (<arsene.gschwind(a)unibas.ch<mailto:arsene.gschwind@unibas.ch>>) escribió: Hi, Do you see the LUNs on the Hypervisor using lsblk or multipath -ll ? rgds, Arsene On Wed, 2019-01-02 at 18:25 +0000, Sebastian Antunez N. wrote: Hello Guys I install 6 host with Ovirt 4.2 connected via FC to Brocade 300 switch and HP EVA P2000 Storage. Zoning was performed on each SAN switch and when creating a Virtual Disk with 3 LUN, but adding the Storage in OVIRT does not see any LUN. The OVIRT nodes were restarted, the Engine but still does not see the LUNs I have searched for information on how to resolve this issue but I have not had any information. I will appreciate your help in this regard as I have not been able to resolve the issue. Thanks to all Regards Sebastian _______________________________________________ Users mailing list -- <mailto:users@ovirt.org> users(a)ovirt.org To unsubscribe send an email to <mailto:users-leave@ovirt.org> users-leave(a)ovirt.org Privacy Statement: <https://www.ovirt.org/site/privacy-policy/> https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: <https://www.ovirt.org/community/about/community-guidelines/> https://www.ovirt.org/community/about/community-guidelines/ List Archives: <https://lists.ovirt.org/archives/list/users@ovirt.org/message/UPILMALCBD5GW…> https://lists.ovirt.org/archives/list/users@ovirt.org/message/UPILMALCBD5GW…

1 0

oVirt Node 4.2.5.1 vm stuck on "Powering Down"
by maoz zadok 03 Jan '19

03 Jan '19

Hello, vm stuck (on two hosts) I have MySQL VM guest that was stuck in a way that "kill -9" to the MySQL server pid did nothing. from the shell I execute "init 0", this did not shut down the VM. from the ovirt-engine I'm trying to power off the machine, and it is not doing anything. the event shows: > VDSM kvm5 command DestroyVDS failed: Virtual machine destroy error > and: > Failed to power off VM mysql-production (Host: kvm5, User: > admin@internal-authz). > Note, when I list the VM s on the hosts view, I see that that same VM is on two hosts (kvm7 and kvm5). It looks like the VM is stuck on two hosts, in the status "Powering Down" any ideas? Thank you

2 4