Ask Your Question

Bruno Domingues's profile - activity

2020-05-22 05:23:39 -0500 received badge  Notable Question (source)
2020-03-24 07:35:27 -0500 received badge  Popular Question (source)
2020-03-23 18:02:47 -0500 received badge  Student (source)
2020-03-22 21:58:59 -0500 commented question Openstack (Queens) instance (VM) running deadly slow

I found the problem. I was using qemu as hypervisor instead of kvm. As soon I changed the configuration into nova, rebooted all nodes and defined host-passthrough into nova config file, it worked like a charm... as fast as my VMWare guest.

2020-03-22 14:42:32 -0500 asked a question Openstack (Queens) instance (VM) running deadly slow

Folks, in a four nodes Openstack (Queens) installation, I am experiencing instances running deadly slowly - It does not matter the size of VM, from 1-8vCPUs and 2-16GB of RAM. Indeed, as bigger the instance the slower is. I am using Sysbench as a reference and tried with Ubuntu 18.04 and CentOS 8.1. Just to have an idea, on nodes with Westmere Intel CPUs with a VM of the same size, one running VMWare ESXi and the other Openstack (KVM/QEMU), the VMWare node runs 10+ times faster and 10+ times lower latency than KVM/QEMU.

Initially, I found that my VMs were identifying the wrong CPU architecture, executing "lscpu" inside the VM showed an AMD EPIC architecture instead of Intel Westmere. However, I already changed the nova.conf cpu_mode=custom and specified cpu_model=Westmere. Now each VM is reporting correctly the CPU architecture.

Operations like "yum update" is taking almost two minutes to start showing up something at the screen and shutting the guest CPU to 100% all time.

Any ideas of what is the root cause of this problem? where should I start looking? debug strategies?

Best Regards! -Bruno Domingues

2017-02-02 07:15:59 -0500 received badge  Famous Question (source)
2016-09-29 08:00:01 -0500 received badge  Notable Question (source)
2016-09-23 09:02:34 -0500 received badge  Popular Question (source)
2016-09-14 21:27:58 -0500 asked a question Could not find requested endpoint in Service Catalog. - Mitaka failed to launch an instance using Ceph as backend

Hi folks, I just installed a small openstack cluster (Mitaka) in a 4 nodes cluster, i.e. 1 controller + 3 compute nodes (classical). I'm running Ceph jewel also as storage for Glance and Cinder as back-end. I was able to upload a CentOS image, raw format, however when I try to launch the instance using this image, I got this message:

Error: Failed to perform requested operation on instance "teste", the instance has an error status: Please try again later [Error: Exceeded maximum number of retries. Exceeded max scheduling attempts 3 for instance bbeb26ff-6cf5-4d67-82a5-c3c3e7dc026d. Last exception: Could not find requested endpoint in Service Catalog.].

Here are my logs: (nova-compute.log)

2016-09-14 15:09:15.206 2617 INFO nova.compute.resource_tracker [req-6fb3b4de-6a81-4d9c-b729-c942381b67ed - - - - -] Compute_service record updated for hyper-node1.lab:hyper-node1.lab
2016-09-14 15:10:14.726 2617 INFO nova.compute.resource_tracker [req-6fb3b4de-6a81-4d9c-b729-c942381b67ed - - - - -] Auditing locally available compute resources for node hyper-node1.lab
2016-09-14 15:10:15.127 2617 INFO nova.compute.resource_tracker [req-6fb3b4de-6a81-4d9c-b729-c942381b67ed - - - - -] Total usable vcpus: 16, total allocated vcpus: 0
2016-09-14 15:10:15.128 2617 INFO nova.compute.resource_tracker [req-6fb3b4de-6a81-4d9c-b729-c942381b67ed - - - - -] Final resource view: name=hyper-node1.lab phys_ram=72317MB used_ram=512MB phys_disk=2105GB used_disk=0GB total_vcpus=16 used_vcpus=0 pci_stats=[]
2016-09-14 15:10:15.162 2617 INFO nova.compute.resource_tracker [req-6fb3b4de-6a81-4d9c-b729-c942381b67ed - - - - -] Compute_service record updated for hyper-node1.lab:hyper-node1.lab
2016-09-14 15:10:16.571 2617 INFO nova.compute.claims [req-597f953d-ed3f-4a92-9631-56fbcb9a79aa 282254a510c744c69eea23234dba3ab0 1c539e1c46244c2c97d7800ed73a4e5b - - -] [instance: bbeb26ff-6cf5-4d67-82a5-c3c3e7dc026d] Attempting claim: memory 2048 MB, disk 20 GB, vcpus 1 CPU
2016-09-14 15:10:16.571 2617 INFO nova.compute.claims [req-597f953d-ed3f-4a92-9631-56fbcb9a79aa 282254a510c744c69eea23234dba3ab0 1c539e1c46244c2c97d7800ed73a4e5b - - -] [instance: bbeb26ff-6cf5-4d67-82a5-c3c3e7dc026d] Total memory: 72317 MB, used: 512.00 MB
2016-09-14 15:10:16.572 2617 INFO nova.compute.claims [req-597f953d-ed3f-4a92-9631-56fbcb9a79aa 282254a510c744c69eea23234dba3ab0 1c539e1c46244c2c97d7800ed73a4e5b - - -] [instance: bbeb26ff-6cf5-4d67-82a5-c3c3e7dc026d] memory limit: 108475.50 MB, free: 107963.50 MB
2016-09-14 15:10:16.572 2617 INFO nova.compute.claims [req-597f953d-ed3f-4a92-9631-56fbcb9a79aa 282254a510c744c69eea23234dba3ab0 1c539e1c46244c2c97d7800ed73a4e5b - - -] [instance: bbeb26ff-6cf5-4d67-82a5-c3c3e7dc026d] Total disk: 2105 GB, used: 0.00 GB
2016-09-14 15:10:16.573 2617 INFO nova.compute.claims [req-597f953d-ed3f-4a92-9631-56fbcb9a79aa 282254a510c744c69eea23234dba3ab0 1c539e1c46244c2c97d7800ed73a4e5b - - -] [instance: bbeb26ff-6cf5-4d67-82a5-c3c3e7dc026d] disk limit: 2105.00 GB, free: 2105.00 GB
2016-09-14 15:10:16.573 2617 INFO nova.compute.claims [req-597f953d-ed3f-4a92-9631-56fbcb9a79aa 282254a510c744c69eea23234dba3ab0 1c539e1c46244c2c97d7800ed73a4e5b - - -] [instance: bbeb26ff-6cf5-4d67-82a5-c3c3e7dc026d] Total vcpu: 16 VCPU, used: 0.00 VCPU
2016-09-14 15:10:16.574 2617 INFO nova.compute.claims [req-597f953d-ed3f-4a92-9631-56fbcb9a79aa 282254a510c744c69eea23234dba3ab0 1c539e1c46244c2c97d7800ed73a4e5b - - -] [instance: bbeb26ff-6cf5-4d67-82a5-c3c3e7dc026d] vcpu limit not specified, defaulting to unlimited
2016-09-14 15:10:16.598 2617 INFO nova.compute.claims [req-597f953d-ed3f-4a92-9631-56fbcb9a79aa 282254a510c744c69eea23234dba3ab0 1c539e1c46244c2c97d7800ed73a4e5b - - -] [instance: bbeb26ff-6cf5-4d67-82a5-c3c3e7dc026d] Claim successful
2016-09-14 15:10:16.829 2617 WARNING nova.virt.osinfo [req-597f953d-ed3f-4a92-9631-56fbcb9a79aa 282254a510c744c69eea23234dba3ab0 1c539e1c46244c2c97d7800ed73a4e5b - - -] Cannot find OS information - Reason: (No configuration information found for operating system Empty)
2016-09-14 15:10:16.857 2617 WARNING nova.virt.osinfo [req-597f953d-ed3f-4a92-9631-56fbcb9a79aa 282254a510c744c69eea23234dba3ab0 1c539e1c46244c2c97d7800ed73a4e5b - - -] Cannot find OS information - Reason: (No configuration information found for operating system Empty)
2016-09-14 15:10:16.993 2617 ERROR nova.compute.manager [req-597f953d-ed3f-4a92-9631-56fbcb9a79aa 282254a510c744c69eea23234dba3ab0 1c539e1c46244c2c97d7800ed73a4e5b - - -] Instance failed network setup after 1 attempt(s)
2016-09-14 15:10:16.993 2617 ERROR nova.compute.manager Traceback (most recent call last):
2016-09-14 15:10:16.993 2617 ERROR nova.compute.manager   File "/usr ...
(more)